Critical Risk →

cache_delete_multi

Delete multiple values from the cache (alias for delete_many).

How to control cache_delete_multi ↓

What cache_delete_multi does on Amazon Location Service MCP Server

AI agents call cache_delete_multi to permanently remove resources in Amazon Location Service MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cache_delete_multi needs a policy

The tool performs bulk deletion of cache entries with no undo mechanism. While cache data is typically transient and lower-impact than persistent data deletion, the irreversible nature of the operation and potential to disrupt service availability by removing critical cached values (e.g., session data, computed results) justifies a 'Destructive' classification.

From the tool's definition Tool name 'cache_delete_multi' and description explicitly states 'Delete multiple values from the cache' — this is an irreversible deletion operation that destroys data.

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

How to control cache_delete_multi

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Location Service MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_delete_multi:

policy.json
{
  "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.

  1. Create a free account and register Amazon Location Service MCP Server — 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_multi

What does the cache_delete_multi tool do? +

Delete multiple values from the cache (alias for delete_many). It is categorised as a Destructive tool in the Amazon Location Service 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 cache_delete_multi? +

Register the Amazon Location Service 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 Amazon Location Service MCP Server. Nothing to install.

What risk level is cache_delete_multi? +

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.

Can I rate-limit cache_delete_multi? +

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.

How do I block cache_delete_multi completely? +

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.

What MCP server provides cache_delete_multi? +

cache_delete_multi is provided by the Amazon Location Service MCP Server MCP server (awslabs.aws-location-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 Amazon Location Service MCP Server tool call.

Start from Amazon Location Service 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 Amazon Location Service MCP Server 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.