identity-entity-delete
AI agents call identity-entity-delete to permanently remove resources in Vault MCP Server (mschuchard) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and fall into the Destructive category. While the description is empty, the tool name combined with the server's Vault administration context makes the destructive nature clear. Deleting identity entities in Vault is a high-severity action as it could compromise access controls and require manual recovery.
From the tool's definition Tool name 'identity-entity-delete' indicates deletion of identity entities in HashiCorp Vault. The 'delete' operation is irreversible.
Attacks that exploit this kind of access
identity-entity-delete. It is categorised as a Destructive tool in the Vault MCP Server (mschuchard) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for identity-entity-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 Vault MCP Server (mschuchard). Nothing to install.
identity-entity-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 identity-entity-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 identity-entity-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.
identity-entity-delete is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →