update_connection · Equinix Fabric MCP: Risk & Policy

WHAT IT DOES

What update_connection does on Equinix Fabric MCP

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

This tool modifies connection parameters within network infrastructure but does not delete or irreversibly destroy data. Bandwidth changes could have operational impact (potentially causing service degradation if misconfigured), justifying 'high' severity. However, changes are reversible through subsequent updates, placing it in Write rather than Destructive.

From the tool's definition Tool description states it "Updates an existing connection" and supports "modifying name, description, bandwidth, and notifications." The verb 'Updates' and the explicit list of modifiable attributes (bandwidth in particular) indicate reversible modification…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_connection Rate-limited

update_connection 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_connection": {
      "limits": [
        {
          "counter": "update_connection_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_connection

What does the update_connection tool do? +

Updates an existing connection. Supports modifying name, description, bandwidth, 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_connection? +

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

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

Can I rate-limit update_connection? +

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

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

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