AI agents call clear_cache to permanently remove resources in OpenAPI Directory MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all cache entries is an irreversible bulk deletion of stored data. While cache can theoretically be rebuilt, the act itself is non-undoable and could disrupt ongoing operations or force expensive recomputation. This qualifies as Destructive with medium severity since cache data is typically regenerable but the action cannot be undone directly.
From the tool's definition 'Clear all cache entries' — irreversibly removes all cached data
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_cache gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenAPI Directory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_cache:
{
"version": "1",
"default": "deny",
"hide": [
"clear_cache"
]
}clear_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear all cache entries. It is categorised as a Destructive tool in the OpenAPI Directory MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenAPI Directory 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 OpenAPI Directory 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 OpenAPI Directory MCP Server MCP server (rawveg/openapi-directory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenAPI Directory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 OpenAPI Directory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.