policy_engine_delete
AI agents call policy_engine_delete 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 in the tool name indicates an irreversible operation. Even without a description, deletion operations are classified as Destructive due to their inability to be undone. In an AWS security policy context, deleting policies could have significant blast radius if triggered unintentionally by an AI agent.
From the tool's definition Tool name 'policy_engine_delete' contains 'delete', indicating irreversible data removal. The empty description prevents full confirmation of scope, but the naming convention strongly suggests deletion of policy engine configurations or data.
Attacks that exploit this kind of access
policy_engine_delete. 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 policy_engine_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 Awslabs Valkey. Nothing to install.
policy_engine_delete 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 policy_engine_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.
Set action: deny in the PolicyLayer policy for policy_engine_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.
policy_engine_delete 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.