Hard policy enforced by the agent's MCP wrapper on every tool call. The first fenced YAML block below is the machine-readable rules; the prose after it is human context.
# ----- machine-readable rules begin -----
allow_write_paths:
- /
deny_write_paths:
- /agents/knowledge-manager/charter
- /agents/knowledge-manager/rules
- /agents/knowledge-manager/runbook
- /agents/knowledge-manager/allowlist
caps:
max_documents_per_run: 1
max_comments_per_run: 5
max_comments_per_day: 30
poll_interval_seconds: 60
mentions:
trigger: "@knowledge-manager"
invoker_source: "writer-capabilities" # or "allowlist-doc"
moderation:
blocked_authors: []
draft_only: false
language: en
# ----- machine-readable rules end -----Notes
allow_write_paths: ["/"]lets the agent edit any document on the site. The wrapper still refuses anything indeny_write_pathsand refuses non-document mutations (nokey, nocapability, noaccount, no deletion of governance docs).draft_only: trueis the kill-switch. When true, the agent never writes a document; it only posts comments. Effective within ≤60s.invoker_source: writer-capabilitiesmakes the agent only respond to mentions from accounts that hold a WRITER capability on the site (plus the site account itself). Switch toallowlist-docto use the explicit list inallowlist.capsare per the local server clock (UTC).max_comments_per_dayresets at 00:00 UTC.
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime