AI agents call delete_entity to permanently remove resources in EspoCRM-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs permanent deletion of database records in EspoCRM. Deletion is inherently irreversible and constitutes a destructive operation. The broad scope ("any entity record") amplifies the risk if an AI agent misuses the tool without proper safeguards, potentially deleting critical business data such as accounts, contacts, cases, or calls. While not financial, the data loss impact justifies 'high' severity.
From the tool's definition Tool name: delete_entity. Description: "Delete any entity record by ID" - the verb "delete" combined with "any entity record" indicates irreversible removal of data without undo capability.
Documented attack patterns abuse exactly the kind of access delete_entity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EspoCRM-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entity:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entity"
]
}delete_entity disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete any entity record by ID. It is categorised as a Destructive tool in the EspoCRM-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for delete_entity: 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 EspoCRM-MCP. Nothing to install.
delete_entity 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_entity 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_entity. 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_entity is provided by the EspoCRM- MCP server (zaphod-black/espomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 EspoCRM-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
46 EspoCRM-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.