import_github_repo · n8n Workflow Builder MCP: Risk & Policy

WHAT IT DOES

What import_github_repo does on n8n Workflow Builder

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

The tool creates or adds new workflow templates to the n8n system, which constitutes modification of data. While importing from a remote source, the primary effect is writing/creating new workflow artifacts locally. It does not execute workflows (Execute), irreversibly delete data (Destructive), or move money (Financial).

From the tool's definition Tool description states 'Import n8n workflow templates from a GitHub repository' — this action retrieves external code/configuration and integrates it into the n8n system, modifying the local workflow state by adding new templates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_github_repo Rate-limited

import_github_repo 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": {
    "import_github_repo": {
      "limits": [
        {
          "counter": "import_github_repo_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 import_github_repo

What does the import_github_repo tool do? +

📦 Import n8n workflow templates from a GitHub repository. 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 import_github_repo? +

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

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

Can I rate-limit import_github_repo? +

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

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

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