delete-serverless-cache

THE RISK

Critical Risk

Why delete-serverless-cache needs a policy

The name unambiguously describes a destructive action—deletion is irreversible. While the empty description prevents full context about what data is affected or whether deletion can be undone, the semantic meaning of 'delete' combined with the destructive nature of cache removal warrants Destructive classification.

From the tool's definition Tool name 'delete-serverless-cache' explicitly indicates deletion of a cache resource. No description provided to clarify scope or reversibility.

Documented attack patterns abuse exactly the kind of access delete-serverless-cache gives an agent:

POLICY

How to control delete-serverless-cache

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-serverless-cache:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-serverless-cache"
  ]
}

delete-serverless-cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Document Loader MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Document Loader MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-serverless-cache

What does the delete-serverless-cache tool do? +

delete-serverless-cache. 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.

How do I enforce a policy on delete-serverless-cache? +

Register the Document Loader MCP Server MCP server in PolicyLayer and add a rule for delete-serverless-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 Document Loader MCP Server. Nothing to install.

What risk level is delete-serverless-cache? +

delete-serverless-cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-serverless-cache? +

Yes. Add a rate_limit block to the delete-serverless-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.

How do I block delete-serverless-cache completely? +

Set action: deny in the PolicyLayer policy for delete-serverless-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.

What MCP server provides delete-serverless-cache? +

delete-serverless-cache 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.

Enforce policy on every Document Loader MCP Server tool call.

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.

CHECK YOUR STACK →