AI agents call delete-cache-cluster 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.
Despite the empty description, the tool name strongly implies permanent deletion of a cloud resource (a cache cluster, likely Redis/Memcached). Deletion is irreversible and constitutes data loss or service disruption. This falls under Destructive rather than Execute because it specifically removes infrastructure rather than executing arbitrary operations.
From the tool's definition Tool name 'delete-cache-cluster' explicitly indicates deletion of a cache cluster resource. The verb 'delete' combined with 'cache-cluster' signals irreversible removal of infrastructure/data.
Documented attack patterns abuse exactly the kind of access delete-cache-cluster 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 delete-cache-cluster:
{
"version": "1",
"default": "deny",
"hide": [
"delete-cache-cluster"
]
}delete-cache-cluster 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-cache-cluster. 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 delete-cache-cluster: 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.
delete-cache-cluster 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 delete-cache-cluster 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 delete-cache-cluster. 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.
delete-cache-cluster 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.