Activate a workflow
AI agents use activate_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.
Activating a workflow changes its operational state and may trigger automatic execution or enable scheduling, affecting system behavior. However, this is reversible (via deactivate_workflow) and does not delete data or move money, placing it in the Write category. Severity is medium because unintended workflow activation could cause undesired automation execution, but the impact is contained to that workflow's scope.
From the tool's definition Tool name 'activate_workflow' and description 'Activate a workflow' indicate state modification of an existing workflow resource. This changes the workflow's active/inactive status, which is a reversible modification (can be deactivated again).
Attacks that exploit this kind of access
Activate a 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 activate_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.
activate_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 activate_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 activate_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.
activate_workflow is provided by the n8n MCP Server MCP server (nikolausm/n8n-mcp-server). 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 →