Critical Risk →

cache_delete

Delete a value from the cache.

How to control cache_delete ↓

What cache_delete does on AWS Labs Aurora DSQL MCP Server

AI agents call cache_delete to permanently remove resources in AWS Labs Aurora DSQL 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 needs a policy

This tool permanently removes data from cache storage with no undo capability. While the blast radius depends on what data is cached (potentially limited to performance artifacts rather than critical business data), the irreversible nature of deletion places it in the Destructive category, which outranks Write.

From the tool's definition Tool name 'cache_delete' and description 'Delete a value from the cache' explicitly indicate irreversible deletion of cached data.

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

How to control cache_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Aurora DSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_delete:

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

cache_delete 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 AWS Labs Aurora DSQL 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

What does the cache_delete tool do? +

Delete a value from the cache. It is categorised as a Destructive tool in the AWS Labs Aurora DSQL 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? +

Register the AWS Labs Aurora DSQL MCP Server MCP server in PolicyLayer and add a rule for cache_delete: 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 Aurora DSQL MCP Server. Nothing to install.

What risk level is cache_delete? +

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

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

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

cache_delete is provided by the AWS Labs Aurora DSQL MCP Server MCP server (awslabs.aurora-dsql-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 Aurora DSQL MCP Server tool call.

Start from AWS Labs Aurora DSQL 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 AWS Labs Aurora DSQL 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.