community_node_install · N8n Fabric MCP: Risk & Policy

WHAT IT DOES

What community_node_install does on N8n Fabric

AI agents invoke community_node_install to trigger actions in N8n Fabric. 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 community_node_install needs a policy

Installing a community node package executes an installation process on the server, introducing third-party code into the n8n environment. This is an Execute-level action because it runs an external package installation with potentially arbitrary code. It has high severity since a malicious or compromised package could compromise the entire automation environment.

From the tool's definition Install a community node package

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

community_node_install Rate-limited

community_node_install 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": {
    "community_node_install": {
      "limits": [
        {
          "counter": "community_node_install_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 Fabric, so you can run agents against it safely.

FAQ

Questions about community_node_install

What does the community_node_install tool do? +

Install a community node package. It is categorised as a Execute tool in the N8n Fabric MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on community_node_install? +

Register the N8n Fabric MCP server in PolicyLayer and add a rule for community_node_install: 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 Fabric. Nothing to install.

What risk level is community_node_install? +

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

Can I rate-limit community_node_install? +

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

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

community_node_install is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.