cache_delete_multi

THE RISK

Critical Risk

Why cache_delete_multi needs a policy

This tool deletes data from cache without the ability to undo the operation. Deletion of multiple cache entries is a destructive operation that cannot be reversed. While the blast radius is somewhat limited to cache (rather than persistent data stores), the irreversible nature of deletion and the potential impact on application state and availability justify the 'Destructive' category and 'high' severity rating.

From the tool's definition Tool name is 'cache_delete_multi' with description 'Delete multiple values from the cache (alias for delete_many)'. The verb 'Delete' combined with 'multi' (multiple) indicates irreversible removal of data.

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

POLICY

How to control cache_delete_multi

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Timestream for InfluxDB 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.

Create a free account and register AWS Labs Timestream for InfluxDB 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

More AWS Labs Timestream for InfluxDB MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint Destructive delete_app delete_app

All 805 AWS Labs Timestream for InfluxDB MCP Server tools →

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 AWS Labs Timestream for InfluxDB 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 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 AWS Labs Timestream for InfluxDB 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 AWS Labs Timestream for InfluxDB 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 AWS Labs Timestream for InfluxDB 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 AWS Labs Timestream for InfluxDB MCP Server MCP server (awslabs.timestream-for-influxdb-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 AWS Labs Timestream for InfluxDB MCP Server tool call.

Start from AWS Labs Timestream for InfluxDB 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 →