delete_instance_in_study
AI agents call delete_instance_in_study to permanently remove resources in Awslabs Valkey — 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 destruction of data or infrastructure. Even without a description, deleting an instance in a study context (particularly in a data/caching system) is a high-blast-radius operation that cannot be undone. This meets the Destructive category definition.
From the tool's definition Tool name 'delete_instance_in_study' contains 'delete', which is an irreversible operation. The context of a MemoryDB/ElastiCache server suggests this removes a database instance or cached data entity. No description provided to clarify scope or reversibility.
Attacks that exploit this kind of access
delete_instance_in_study. It is categorised as a Destructive tool in the Awslabs Valkey MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Valkey 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 Awslabs Valkey. Nothing to install.
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.
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.
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.
delete_instance_in_study is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.