delete_person
Delete a person from Twenty CRM
This record as markdown: /tools/denisalmeida-twenty-crm-mcp/delete-person.md
What delete_person does on Twenty CRM MCP Server
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.
Why delete_person is rated Critical
Deletion operations are categorized as Destructive per the classification rules. The tool permanently removes person records from the CRM system. While the blast radius is limited to a single person record (not a financial transaction or system-wide cascade), the irreversibility and data loss nature warrants 'high' severity. Confidence is high because the intent is explicit and unambiguous.
From the tool's definition Tool name is 'delete_person' and description states 'Delete a person from Twenty CRM' — this is an irreversible deletion operation that removes data that cannot be recovered without backup restoration.
Attacks that exploit this kind of access
The rule that runs delete_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty CRM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_person, this is the rule to start with:
delete_person is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Twenty CRM MCP Server, apply this rule, and every delete_person call is checked against it from then on.
Questions about delete_person
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 (denisalmeida/twenty-crm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty CRM MCP Server, and thousands of servers like it.
Across the catalogue