AI agents use deactivate_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.
Deactivating a workflow changes its state (active to inactive), which is a reversible modification — the workflow can be reactivated. This is a state update/write operation, not destructive since no data is deleted. However, misuse could disrupt automated processes relying on the workflow, hence medium severity.
From the tool's definition Deactivate a workflow in n8n
Documented attack patterns abuse exactly the kind of access deactivate_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and n8n MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deactivate_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"deactivate_workflow": {
"limits": [
{
"counter": "deactivate_workflow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}deactivate_workflow 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.
Deactivate a workflow in n8n. 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 deactivate_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.
deactivate_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 deactivate_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 deactivate_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.
deactivate_workflow is provided by the n8n MCP Server MCP server (leonardsellem/n8n-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from n8n 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.
11 n8n MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.