delete-cache-cluster
AI agents call delete-cache-cluster to permanently remove resources in AWS Labs Amazon Neptune MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name contains 'delete' which is a destructive operation that irreversibly removes a cache cluster. Even though the description is empty, the function name alone clearly indicates this performs a deletion that cannot be undone. The blast radius is high because deleting a cache cluster can disrupt application availability and data access patterns.
From the tool's definition Tool name 'delete-cache-cluster' explicitly indicates deletion operation on a cache cluster resource.
Documented attack patterns abuse exactly the kind of access delete-cache-cluster gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Amazon Neptune MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-cache-cluster:
{
"version": "1",
"default": "deny",
"hide": [
"delete-cache-cluster"
]
} delete-cache-cluster disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete-cache-cluster. It is categorised as a Destructive tool in the AWS Labs Amazon Neptune MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs Amazon Neptune MCP Server MCP server in PolicyLayer and add a rule for delete-cache-cluster: 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 Amazon Neptune MCP Server. Nothing to install.
delete-cache-cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-cache-cluster 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.
Set action: deny in the PolicyLayer policy for delete-cache-cluster. 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.
delete-cache-cluster is provided by the AWS Labs Amazon Neptune MCP Server MCP server (awslabs.amazon-neptune-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs Amazon Neptune 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 Amazon Neptune MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.