Initialize and populate empty AI_README files within a project. When to use: - First-time setup when no AI_README exists. - get_context_for_file reports empty or missing AI_README files. - Newly created directories need conventions recorded. - Multiple directories require conventions in one pass....
Admin/system-level operation
Part of the Ai Readme MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call init_ai_readme to permanently remove or destroy resources in Ai Readme. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call init_ai_readme in a loop, permanently destroying resources in Ai Readme. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
init_ai_readme:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Ai Readme policy for all 6 tools.
Agents calling destructive-class tools like init_ai_readme have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
init_ai_readme is one of the critical-risk operations in Ai Readme. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Initialize and populate empty AI_README files within a project. When to use: - First-time setup when no AI_README exists. - get_context_for_file reports empty or missing AI_README files. - Newly created directories need conventions recorded. - Multiple directories require conventions in one pass. What it does: - Scans for missing or empty AI_README documents. - Creates a root-level AI_README if none is present. - Provides directory-specific prompts to gather conventions. - Guides you through documenting tech stack, patterns, and naming. Workflow: - Call init_ai_readme. - Follow the step-by-step instructions to inspect each directory. - Use update_ai_readme to record the conventions. - Run validate_ai_readmes to check for problems. - Fix any warnings (remove redundant content, add Cross-directory dependencies section). - Re-run get_context_for_file to confirm coverage before coding.. It is categorised as a Destructive tool in the Ai Readme MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for init_ai_readme. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ai Readme MCP server.
init_ai_readme is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the init_ai_readme rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for init_ai_readme. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
init_ai_readme is provided by the Ai Readme MCP server (ai-readme-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept