Medium Risk

update_ai_readme

CALL THIS to record DECISIONS and CONVENTIONS. WHEN TO CALL: A. CONFLICT RESOLUTION — STOP IMMEDIATELY when any of these occur: - User says: "don't use X", "use Y instead", "prefer", "switch to". - During planning: user's request or your proposal differs from AI_README conventions. - During pla...

Accepts raw HTML/template content (operations[].content); Single-target operation

Part of the Ai Readme MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ai-readme-mcp Write Risk 2/5

AI agents use update_ai_readme to create or modify resources in Ai Readme. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update_ai_readme repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ai Readme.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

ai-readme.yaml
tools:
  update_ai_readme:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Ai Readme policy for all 6 tools.

Tool Name update_ai_readme
Category Write
Risk Level Medium

Agents calling write-class tools like update_ai_readme have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update_ai_readme tool do? +

CALL THIS to record DECISIONS and CONVENTIONS. WHEN TO CALL: A. CONFLICT RESOLUTION — STOP IMMEDIATELY when any of these occur: - User says: "don't use X", "use Y instead", "prefer", "switch to". - During planning: user's request or your proposal differs from AI_README conventions. - During planning: user approves a plan that contradicts AI_README. - User overrides a convention mid-task (even casually, e.g. 'just use X here'). - DO NOT continue planning or coding. Call update_ai_readme first, then resume. B. ARCHITECTURAL DECISIONS (during planning/implementation): - You chose a design pattern (e.g., repository pattern, factory, singleton). - You decided on API structure (REST paths, error format, response shape). - You established naming conventions (files, functions, variables). - You created new abstractions (utilities, hooks, services, types). - You set up error handling strategy or validation approach. - You introduced a new dependency or integration pattern. C. IMPLEMENTATION PATTERNS (after writing code): - You created a reusable pattern others should follow. - You established a file/folder structure for a new feature. - You made decisions that affect future development. RULE: If a decision will affect MORE THAN ONE FILE or FUTURE CODE → RECORD IT. WORKFLOW: 1. get_context (read current conventions). 2. Make decision or detect conflict. 3. update_ai_readme (record the decision). 4. Continue with implementation. Content Rules: - Extremely concise (< 400 tokens). - Only actionable conventions (tech, naming, patterns, infrastructure patterns, testing patterns). - NO explanations or examples. It is categorised as a Write tool in the Ai Readme MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_ai_readme? +

Add a rule in your Intercept YAML policy under the tools section for update_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.

What risk level is update_ai_readme? +

update_ai_readme is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_ai_readme? +

Yes. Add a rate_limit block to the update_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.

How do I block update_ai_readme completely? +

Set action: deny in the Intercept policy for update_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.

What MCP server provides update_ai_readme? +

update_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.

Enforce policies on Ai Readme

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.