deactivate_workflow · N8n MCP: Risk & Policy

WHAT IT DOES

What deactivate_workflow does on N8n

AI agents use deactivate_workflow to create or update resources in N8n — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N8n environment.

WHY IT NEEDS A POLICY

Why deactivate_workflow needs a policy

Deactivating a workflow modifies its configuration (stops triggers) but does not delete data or irreversibly destroy anything. It is reversible via the activate_workflow tool (present on the sibling tools list). While it affects operational state, the change can be undone without data loss, placing it in the Write category rather than Destructive.

From the tool's definition Tool description states 'Deactivate a workflow so its triggers stop running. Requires write_mode.' This is a state modification operation that changes workflow behavior reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deactivate_workflow Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deactivate_workflow": {
      "limits": [
        {
          "counter": "deactivate_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches N8n, so you can run agents against it safely.

FAQ

Questions about deactivate_workflow

What does the deactivate_workflow tool do? +

Deactivate a workflow so its triggers stop running. Requires write_mode. It is categorised as a Write tool in the N8n MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on deactivate_workflow? +

Register the N8n 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. Nothing to install.

What risk level is deactivate_workflow? +

deactivate_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deactivate_workflow? +

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.

How do I block deactivate_workflow completely? +

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.

What MCP server provides deactivate_workflow? +

deactivate_workflow is provided by the N8n MCP server (siddharth0903/n8n-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.