AI agents call delete_person to permanently remove resources in Twenty CRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes person records from the CRM system without the ability to undo the action. Deletion of customer data is irreversible and represents a destructive operation with significant business impact. High severity reflects the potential loss of critical customer information and associated business relationships.
From the tool's definition Tool name 'delete_person' and description 'Delete a person from Twenty CRM' explicitly indicate irreversible deletion of customer data records.
Documented attack patterns abuse exactly the kind of access delete_person gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_person:
{
"version": "1",
"default": "deny",
"hide": [
"delete_person"
]
}delete_person 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 a person from Twenty CRM. It is categorised as a Destructive tool in the Twenty CRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Twenty CRM MCP Server MCP server in PolicyLayer and add a rule for delete_person: 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 Twenty CRM MCP Server. Nothing to install.
delete_person 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_person 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_person. 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_person is provided by the Twenty CRM MCP Server MCP server (mhenry3164/twenty-crm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twenty CRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Twenty CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.