Clear the MTA:SA documentation cache for a specific function or all functions.
AI agents call clear_cache to permanently remove resources in MTA:SA Documentation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache irreversibly removes cached data, requiring it to be rebuilt. While the underlying documentation is not lost (it can be re-fetched), the cache data itself is destroyed without recovery. The blast radius is low since only a local/server-side documentation cache is affected — no user data, financial records, or production systems are impacted.
From the tool's definition 'Clear the MTA:SA documentation cache for a specific function or all functions'
Attacks that exploit this kind of access
Clear the MTA:SA documentation cache for a specific function or all functions. It is categorised as a Destructive tool in the MTA:SA Documentation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MTA:SA Documentation MCP Server MCP server in PolicyLayer and add a rule for clear_cache: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MTA:SA Documentation MCP Server. Nothing to install.
clear_cache 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 clear_cache rule in your PolicyLayer 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 PolicyLayer policy for clear_cache. 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.
clear_cache is provided by the MTA:SA Documentation MCP Server MCP server (mtasa-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →