Create One workflowAutomatedTrigger
AI agents use createOneWorkflowAutomatedTrigger to create or update resources in Twenty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twenty MCP Server environment.
This tool creates (writes) a new workflow automation trigger in the Twenty CRM system. While it modifies system state, the operation is reversible—triggers can be modified or deleted afterward.
From the tool's definition Tool name 'createOneWorkflowAutomatedTrigger' explicitly indicates creation of a workflow automation trigger. The description states 'Create One workflowAutomatedTrigger', confirming a write operation that adds new data to the CRM system.
Documented attack patterns abuse exactly the kind of access createOneWorkflowAutomatedTrigger 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 createOneWorkflowAutomatedTrigger:
{
"version": "1",
"default": "deny",
"tools": {
"createOneWorkflowAutomatedTrigger": {
"limits": [
{
"counter": "createoneworkflowautomatedtrigger_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createOneWorkflowAutomatedTrigger stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create One workflowAutomatedTrigger. It is categorised as a Write tool in the Twenty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for createOneWorkflowAutomatedTrigger: 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.
createOneWorkflowAutomatedTrigger is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createOneWorkflowAutomatedTrigger 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 createOneWorkflowAutomatedTrigger. 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.
createOneWorkflowAutomatedTrigger 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.