update_fabric_router · Equinix Fabric MCP: Risk & Policy

WHAT IT DOES

What update_fabric_router does on Equinix Fabric MCP

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

This tool modifies cloud router attributes in a controlled, non-destructive manner. While 'package' changes could have operational implications for network routing, the operations are reversible (can be re-updated). This is classic Write behavior.

From the tool's definition Tool description explicitly states 'Update an existing Fabric Cloud Router' and 'modifying name, description, package, and notifications' — these are reversible modifications to infrastructure configuration, not deletion or destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_fabric_router Rate-limited

update_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": {
    "update_fabric_router": {
      "limits": [
        {
          "counter": "update_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 update_fabric_router

What does the update_fabric_router tool do? +

Update an existing Fabric Cloud Router. Supports modifying name, description, package, and notifications. 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 update_fabric_router? +

Register the Equinix Fabric MCP server in PolicyLayer and add a rule for update_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 update_fabric_router? +

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

Can I rate-limit update_fabric_router? +

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

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

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