Create a new workflow
AI agents use create_workflow to create or update resources in n8n MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n MCP Server environment.
Creating a workflow is a reversible write operation that adds new data to the system. While workflows can be complex and affect downstream operations when activated, the act of creation alone is Write-category. The severity is high because a malicious workflow could be created to perform harmful actions when activated, making this a significant risk even though the operation itself is reversible via deletion.
From the tool's definition Tool name is 'create_workflow' and description states 'Create a new workflow'. This creates new data (a workflow) in the n8n automation platform.
Attacks that exploit this kind of access
Create a new workflow. It is categorised as a Write tool in the n8n MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the n8n MCP Server 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 MCP Server. 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 MCP Server MCP server (sandreotti/n8n-mcp). 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 →