delete_schedule
AI agents call delete_schedule 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.
The 'delete' verb indicates an irreversible operation that removes data or configuration. While the description is empty (lowering confidence somewhat), the tool name strongly suggests deletion of a schedule—a destructive action that cannot be undone without manual recreation.
From the tool's definition Tool name 'delete_schedule' indicates deletion of a schedule resource; no description provided to clarify scope or reversibility, but the verb 'delete' combined with AWS ElastiCache context suggests irreversible removal of a configured schedule.
Attacks that exploit this kind of access
delete_schedule. 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.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for delete_schedule: 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.
delete_schedule 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_schedule 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_schedule. 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_schedule 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.