create_fabric_router · Equinix Fabric MCP: Risk & Policy

WHAT IT DOES

What create_fabric_router does on Equinix Fabric MCP

AI agents use create_fabric_router to create or update resources in Equinix Fabric MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Equinix Fabric MCP environment.

WHY IT NEEDS A POLICY

Why create_fabric_router needs a policy

The tool creates a new network resource (Fabric Cloud Router) in a specified metro location, which is a reversible data modification operation. While the blast radius is high due to potential network topology changes and BGP routing impacts, it does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger external operations beyond provisioning infrastructure.

From the tool's definition Tool name 'create_fabric_router' and description states 'Create a new Fabric Cloud Router' — this is a creation operation that establishes new network infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_fabric_router Rate-limited

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

FAQ

Questions about create_fabric_router

What does the create_fabric_router tool do? +

Create a new Fabric Cloud Router in a specified metro location. Cloud Routers enable dynamic Layer 3 routing between multiple connections using BGP. It is categorised as a Write tool in the Equinix Fabric MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_fabric_router? +

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

What risk level is create_fabric_router? +

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

Can I rate-limit create_fabric_router? +

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

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

create_fabric_router is provided by the Equinix Fabric MCP server (sliuuu/equinix-fabric-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.