Delete One workflowAutomatedTrigger
AI agents call deleteOneWorkflowAutomatedTrigger 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.
This tool permanently removes a workflow automation trigger from the CRM system. Deletion is an irreversible operation with no undo capability. In a CRM context, removing automation triggers could disrupt critical business processes (email notifications, task assignments, etc.). An AI agent with unrestricted access could maliciously delete important workflow automations, causing operational damage.
From the tool's definition Tool name 'deleteOneWorkflowAutomatedTrigger' uses 'delete' verb and description states 'Delete One workflowAutomatedTrigger'. The 'delete' operation is irreversible and cannot be undone.
Documented attack patterns abuse exactly the kind of access deleteOneWorkflowAutomatedTrigger gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteOneWorkflowAutomatedTrigger:
{
"version": "1",
"default": "deny",
"hide": [
"deleteOneWorkflowAutomatedTrigger"
]
}deleteOneWorkflowAutomatedTrigger 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 One workflowAutomatedTrigger. 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 deleteOneWorkflowAutomatedTrigger: 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.
deleteOneWorkflowAutomatedTrigger 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 deleteOneWorkflowAutomatedTrigger 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 deleteOneWorkflowAutomatedTrigger. 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.
deleteOneWorkflowAutomatedTrigger 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.
Start from Twenty 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.
219 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.