✨ Create a new workflow in n8n. Provide workflow name, nodes, and connections.
AI agents use create_workflow to create or update resources in n8n Workflow Builder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n Workflow Builder environment.
Creating a new workflow is a reversible write operation that modifies the n8n system state by adding new automation artifacts. While workflows can execute arbitrary operations on connected systems, the tool itself is classified by its direct action (creating workflow definitions), not the potential side effects of those workflows when executed.
From the tool's definition Tool description explicitly states 'Create a new workflow in n8n. Provide workflow name, nodes, and connections.' The verb 'create' and description of adding new workflow artifacts indicates data creation/modification.
Attacks that exploit this kind of access
✨ Create a new workflow in n8n. Provide workflow name, nodes, and connections. It is categorised as a Write tool in the n8n Workflow Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for create_workflow: 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 n8n Workflow Builder. Nothing to install.
create_workflow 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 create_workflow 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 create_workflow. 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.
create_workflow is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →