Critical Risk →

cache_delete_many

Delete multiple values from the cache.

How to control cache_delete_many ↓

What cache_delete_many does on Awslabs Amazon Sns Sqs

AI agents call cache_delete_many to permanently remove resources in Awslabs Amazon Sns Sqs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cache_delete_many needs a policy

This tool deletes data without reversibility. Although described in a cache context rather than persistent storage, deletion of cache entries is destructive and cannot be undone. The 'many' suffix suggests batch deletion, increasing blast radius if misused by an agent (e.g., deleting critical cached application state). This exceeds Write (which modifies reversibly) and warrants Destructive classification.

From the tool's definition Tool name 'cache_delete_many' and description 'Delete multiple values from the cache' indicate irreversible deletion of data at scale.

Documented attack patterns abuse exactly the kind of access cache_delete_many gives an agent:

How to control cache_delete_many

PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_delete_many:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cache_delete_many"
  ]
}

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

  1. Create a free account and register Awslabs Amazon Sns Sqs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cache_delete_many

What does the cache_delete_many tool do? +

Delete multiple values from the cache. It is categorised as a Destructive tool in the Awslabs Amazon Sns Sqs 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 cache_delete_many? +

Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for cache_delete_many: 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is cache_delete_many? +

cache_delete_many 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 cache_delete_many? +

Yes. Add a rate_limit block to the cache_delete_many 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 cache_delete_many completely? +

Set action: deny in the PolicyLayer policy for cache_delete_many. 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 cache_delete_many? +

cache_delete_many is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-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 Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.