Activate a workflow
AI agents use workflow_activate to create or update resources in N8n Fabric — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N8n Fabric environment.
Activating a workflow is a reversible state change (it can be deactivated), so it falls under Write rather than Execute. However, severity is high because activating a workflow enables automated execution of potentially complex or impactful automation chains in an n8n environment, which could trigger downstream operations including financial, destructive, or external actions depending on workflow content.
From the tool's definition 'Activate a workflow' — changes the state of a workflow from inactive to active, enabling it to run automatically on triggers
Attacks that exploit this kind of access
Activate a workflow. It is categorised as a Write tool in the N8n Fabric MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N8n Fabric MCP server in PolicyLayer and add a rule for workflow_activate: 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 Fabric. Nothing to install.
workflow_activate 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 workflow_activate 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 workflow_activate. 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.
workflow_activate is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). 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 →