Delete multiple values from the cache (alias for delete_many).
AI agents call cache_delete_multi to permanently remove resources in Document Loader MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes cached data without possibility of recovery. Even though the blast radius is limited to cache (not persistent primary data), the irreversible nature of deletion and the 'multiple values' scope elevate it to Destructive category. Severity is high rather than critical because cache corruption is typically recoverable through cache rebuild, but the tool still cannot be undone once executed.
From the tool's definition Tool name 'cache_delete_multi' and description 'Delete multiple values from the cache' explicitly indicate irreversible deletion of data. The verb 'Delete' and phrase 'delete_many' confirm destructive intent.
Documented attack patterns abuse exactly the kind of access cache_delete_multi gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Document Loader MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_delete_multi:
{
"version": "1",
"default": "deny",
"hide": [
"cache_delete_multi"
]
}cache_delete_multi 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.
Delete multiple values from the cache (alias for delete_many). It is categorised as a Destructive tool in the Document Loader MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Document Loader MCP Server MCP server in PolicyLayer and add a rule for cache_delete_multi: 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 Document Loader MCP Server. Nothing to install.
cache_delete_multi 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 cache_delete_multi 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 cache_delete_multi. 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.
cache_delete_multi is provided by the Document Loader MCP Server MCP server (awslabs.document-loader-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Document Loader 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.
805 Document Loader MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.