delete_instance_in_study

delete_instance_in_study

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

What delete_instance_in_study does on Amazon ElastiCache Memcached MCP Server

AI agents call delete_instance_in_study 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 delete_instance_in_study needs a policy

Even though the description is uninformative, the verb 'delete' combined with 'instance' indicates this tool removes data permanently. In an ElastiCache Memcached context, deleting an instance destroys that resource and any associated data. This is an irreversible action with no undo capability, placing it in the Destructive category.

From the tool's definition Tool name 'delete_instance_in_study' indicates irreversible deletion of a study instance. The description is empty, but the name alone strongly suggests a destructive operation that cannot be undone.

Questions about delete_instance_in_study

What does the delete_instance_in_study tool do? +

delete_instance_in_study. 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 delete_instance_in_study? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for delete_instance_in_study: 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 delete_instance_in_study? +

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

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

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

delete_instance_in_study 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.