deleteOneWorkflow
A destructive tool on the Twenty MCP server.
This record as markdown: /tools/jdu278-twenty-mcp-server/deleteoneworkflow.md
What deleteOneWorkflow does on Twenty MCP Server
AI agents call deleteOneWorkflow to permanently remove resources in Twenty MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteOneWorkflow is rated Critical
This tool irreversibly removes a workflow from the Twenty CRM system. Workflows typically represent business logic automations or processes, so deletion cannot be undone and constitutes a destructive operation. The blast radius depends on the workflow's scope and dependencies, warranting 'high' severity rather than 'critical' since it targets a single workflow rather than bulk deletion or system-critical data.
From the tool's definition Tool name is 'deleteOneWorkflow' with description 'Delete One workflow'. The verb 'delete' combined with the singular object 'One workflow' indicates irreversible deletion of a specific workflow record.
Attacks that exploit this kind of access
The rule that runs deleteOneWorkflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteOneWorkflow, this is the rule to start with:
deleteOneWorkflow 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 MCP Server, apply this rule, and every deleteOneWorkflow call is checked against it from then on.
Questions about deleteOneWorkflow
deleteOneWorkflow is a destructive tool on the Twenty MCP Server MCP server. It is categorised as a Destructive tool in the Twenty MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for deleteOneWorkflow: 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 MCP Server. Nothing to install.
deleteOneWorkflow 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 deleteOneWorkflow 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 deleteOneWorkflow. 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.
deleteOneWorkflow is provided by the Twenty MCP Server MCP server (jdu278/twenty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty MCP Server, and thousands of servers like it.
Across the catalogue