create_change_request · n8n Workflow Builder MCP

WHAT IT DOES

What create_change_request does on n8n Workflow Builder

AI agents use create_change_request 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 create_change_request needs a policy

The tool creates a change request record—a reversible write operation that initiates an approval workflow. While it doesn't immediately modify production workflows or execute code, it creates a persistent record in a workflow management system that will be acted upon.

From the tool's definition Tool explicitly performs 'Create change request' which is a write action that documents and creates a new artifact (change request) in the workflow system. This involves creating reversible data structures ('documents changes, requester, reason.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_change_request Rate-limited

create_change_request 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": {
    "create_change_request": {
      "limits": [
        {
          "counter": "create_change_request_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 create_change_request

What does the create_change_request tool do? +

📝 Create change request for approval workflow: documents changes, requester, reason. Returns request ID for tracking. 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 create_change_request? +

Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for create_change_request: 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 create_change_request? +

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

Can I rate-limit create_change_request? +

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

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

create_change_request 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.