gateway_delete

gateway_delete

Server Amazon ElastiCache Memcached MCP Server awslabs.memcached-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What gateway_delete does on Amazon ElastiCache Memcached MCP Server

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

Why gateway_delete needs a policy

Delete operations are classified as Destructive because they remove data irreversibly and cannot be undone. Even without a description, the 'delete' verb in the tool name indicates this is a destructive action. Severity is high because deleting gateway infrastructure in a production ElastiCache cluster could disrupt service availability and data access.

From the tool's definition Tool name is 'gateway_delete' which uses the verb 'delete', indicating irreversible removal of data. The tool description is empty, preventing confirmation of scope, but the name alone strongly suggests deletion of AWS ElastiCache gateway resources.

Questions about gateway_delete

What does the gateway_delete tool do? +

gateway_delete. It is categorised as a Destructive tool in the Amazon ElastiCache Memcached 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 gateway_delete? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for gateway_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 Amazon ElastiCache Memcached MCP Server. Nothing to install.

What risk level is gateway_delete? +

gateway_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 gateway_delete? +

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

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

gateway_delete is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.