review_change_request · n8n Workflow Builder MCP

WHAT IT DOES

What review_change_request does on n8n Workflow Builder

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

This tool modifies the state of a change request by adding reviewer information, comments, and updating status. These are reversible data modifications (status can be changed again, comments can be updated), placing it in the Write category. Misuse could disrupt workflow approval processes but is not irreversible.

From the tool's definition Approve or reject change request: adds reviewer, comments, updates status

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

review_change_request Rate-limited

review_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": {
    "review_change_request": {
      "limits": [
        {
          "counter": "review_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 review_change_request

What does the review_change_request tool do? +

✅ Approve or reject change request: adds reviewer, comments, updates status. 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 review_change_request? +

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

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

Can I rate-limit review_change_request? +

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

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

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