identity_delete_api_key_provider
AI agents call identity_delete_api_key_provider 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' action in the tool name indicates this operation irreversibly removes an API key provider, which cannot be undone. This is a destructive operation affecting authentication infrastructure. The empty description reduces confidence slightly, but the clear 'delete' semantics in the name are sufficiently indicative of destructive capability.
From the tool's definition Tool name 'identity_delete_api_key_provider' contains 'delete', indicating irreversible removal of an API key provider identity resource.
Attacks that exploit this kind of access
identity_delete_api_key_provider. 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 identity_delete_api_key_provider: 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.
identity_delete_api_key_provider 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 identity_delete_api_key_provider 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 identity_delete_api_key_provider. 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.
identity_delete_api_key_provider 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.