update_workflow · n8n Workflow Builder MCP: Risk & Policy

WHAT IT DOES

What update_workflow does on n8n Workflow Builder

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

WHY IT NEEDS A POLICY

Why update_workflow needs a policy

This tool creates or modifies data reversibly (a core Write category characteristic). While the description is truncated, 'update' combined with 'modify workflow properties' demonstrates reversible data modification. Severity is high because workflows in n8n orchestrate integrations across systems; unauthorized modifications could disrupt critical automation, alter data flows, or introduce security vulnerabilities.

From the tool's definition Tool name is 'update_workflow' and description states 'Update an existing workflow. Modify workflow properties like name' — clearly modifies existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_workflow Rate-limited

update_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": {
    "update_workflow": {
      "limits": [
        {
          "counter": "update_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 Workflow Builder, so you can run agents against it safely.

FAQ

Questions about update_workflow

What does the update_workflow tool do? +

✏️ Update an existing workflow. Modify workflow properties like name,. It is categorised as a Write tool in the n8n Workflow Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_workflow? +

Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for update_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 Workflow Builder. Nothing to install.

What risk level is update_workflow? +

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

Can I rate-limit update_workflow? +

Yes. Add a rate_limit block to the update_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 update_workflow completely? +

Set action: deny in the PolicyLayer policy for update_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 update_workflow? +

update_workflow is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.