Permanently delete an identity and all its data (inbox, vault, logs)
AI agents call identities_delete to permanently remove resources in Mailgent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes multiple data structures (identity record, inbox messages, credential vault, audit logs) with no undo capability. The permanent nature and broad scope of deletion make it Destructive rather than Write.
From the tool's definition Tool description explicitly states 'Permanently delete an identity and all its data (inbox, vault, logs)' — the word 'Permanently' and the scope of deletion (identity, inbox, vault, logs) clearly indicates irreversible data destruction.
Attacks that exploit this kind of access
Permanently delete an identity and all its data (inbox, vault, logs). It is categorised as a Destructive tool in the Mailgent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for identities_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 Mailgent MCP Server. Nothing to install.
identities_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 identities_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 identities_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.
identities_delete is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-mcp). 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 →