Managing Banned AST Patterns

Ban rules are discovered from two sources, both checked by the preToolUse hook:

1. $HOME/.BANNED_AST.md — global rules that apply to all edits, regardless of project.
2. BANNED_AST.md files in any parent directory of the edited file — can contain multiple rules, scoped to that subtree.

Source 1: Global Ban File ($HOME/.BANNED_AST.md)

Place a BANNED_AST.md in your home directory to define rules that apply globally to every edit. It uses the same multi-rule format as directory-scoped files:

---
name: no-eval
message: "Do not use eval(). It poses a security risk and should be replaced with safer alternatives."
---