Pull changes from source control
AI agents invoke n8n_pull_source_control to trigger actions in n8n MCP Server. 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.
Pulling from source control is an external operation that fetches and applies remote changes to the local n8n instance, potentially overwriting workflows, credentials, and configurations. It triggers an external git operation and modifies the system state, making it Execute-level.
From the tool's definition Pull changes from source control
Attacks that exploit this kind of access
Pull changes from source control. It is categorised as a Execute tool in the n8n MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the n8n MCP Server MCP server in PolicyLayer and add a rule for n8n_pull_source_control: 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 MCP Server. Nothing to install.
n8n_pull_source_control is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the n8n_pull_source_control 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.
Set action: deny in the PolicyLayer policy for n8n_pull_source_control. 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.
n8n_pull_source_control is provided by the n8n MCP Server MCP server (shravan1610/n8n-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →