cache_delete_many

Delete multiple values from the cache. Args: keys: List of keys to delete Returns: Success message or error message

SERVERAWS SOURCE@awslabs/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/cache-delete-many.md

WHAT IT DOES

What cache_delete_many does on AWS

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

RISK

Why cache_delete_many is rated Critical

This tool permanently removes cached data without reversibility. While the blast radius is limited to cache (not primary data), the destructive nature of deletion and inability to undo the operation places it in the Destructive category, which takes precedence over Write.

From the tool's definition Tool name 'cache_delete_many' and description 'Delete multiple values from the cache' indicate irreversible deletion of data. The operation cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cache_delete_many safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cache_delete_many, this is the rule to start with:

cache_delete_many Hidden

cache_delete_many is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every cache_delete_many call is checked against it from then on.

FAQ

Questions about cache_delete_many

What does the cache_delete_many tool do? +

Delete multiple values from the cache. Args: keys: List of keys to delete Returns: Success message or error message. It is categorised as a Destructive tool in the AWS 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 AWS 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 AWS. 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 AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →