Compress an AI_README.md file using deterministic filler-language removal (no LLM call). WHEN TO CALL: - validate_ai_readmes reports 'filler-language' warnings. - validate_ai_readmes reports token count is too high. - After init_ai_readme, to tighten up generated content. - Any time you want to ...
Part of the Ai Readme MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call compress_ai_readme to retrieve information from Ai Readme without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though compress_ai_readme only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
compress_ai_readme:
rules:
- action: allowSee the full Ai Readme policy for all 6 tools.
Agents calling read-class tools like compress_ai_readme have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Compress an AI_README.md file using deterministic filler-language removal (no LLM call). WHEN TO CALL: - validate_ai_readmes reports 'filler-language' warnings. - validate_ai_readmes reports token count is too high. - After init_ai_readme, to tighten up generated content. - Any time you want to reduce AI_README token footprint without losing information. WHAT IT DOES (pure text transforms, deterministic): - Removes filler: just, really, basically, actually, simply, essentially - Shortens verbose phrases: 'in order to' → 'to', 'utilize' → 'use', 'make sure to' → 'ensure' - Removes hedging: 'you should', 'remember to', 'it might be worth', 'please note that' - Removes fluff connectives: furthermore, additionally, in addition, moreover - NEVER modifies: code blocks (``` fenced), inline code (`...`), headings, file paths, URLs, commands - Output may contain sentence fragments — this is intentional. Fragments are valid token-efficient format. USE dryRun:true FIRST to preview changes before writing.. It is categorised as a Read tool in the Ai Readme MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for compress_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.
compress_ai_readme is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compress_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 compress_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.
compress_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