source_control_pull · N8n MCP: Risk & Policy

WHAT IT DOES

What source_control_pull does on N8n

AI agents invoke source_control_pull to trigger actions in N8n. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why source_control_pull needs a policy

Pulling from a Git repository triggers an external operation that modifies the local n8n environment by applying remote changes (workflows, credentials, configurations) from the repository. This is not a simple write/create operation—it executes a Git pull which can overwrite existing workflows and settings in a potentially irreversible way.

From the tool's definition Pull changes from the connected Git repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

source_control_pull Rate-limited

source_control_pull stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "source_control_pull": {
      "limits": [
        {
          "counter": "source_control_pull_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 source_control_pull

What does the source_control_pull tool do? +

Pull changes from the connected Git repository. Requires write_mode and source control configured. It is categorised as a Execute tool in the N8n MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on source_control_pull? +

Register the N8n MCP server in PolicyLayer and add a rule for source_control_pull: 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 source_control_pull? +

source_control_pull is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit source_control_pull? +

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

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

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