delete_conversa
Delete a conversa from Twenty CRM
This record as markdown: /tools/denisalmeida-twenty-crm-mcp/delete-conversa.md
What delete_conversa does on Twenty CRM MCP Server
AI agents call delete_conversa 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_conversa is rated Critical
This tool permanently removes a conversation record from the CRM system with no undo capability. The action cannot be reversed and results in data loss. Deletion operations are classified as Destructive, which is more severe than Write operations.
From the tool's definition Tool name 'delete_conversa' and description 'Delete a conversa from Twenty CRM' indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_conversa 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_conversa, this is the rule to start with:
delete_conversa 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_conversa call is checked against it from then on.
Questions about delete_conversa
Delete a conversa 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_conversa: 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_conversa 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_conversa 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_conversa. 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_conversa 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