delete_connection

Deletes a Fabric connection. This action cannot be undone and will terminate the connection.

Server Equinix Fabric MCP sliuuu/equinix-fabric-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_connection does on Equinix Fabric MCP

AI agents call delete_connection to permanently remove resources in Equinix Fabric MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_connection needs a policy

This tool permanently removes network connections with no ability to recover. While not financial in nature, the irreversible deletion of production network infrastructure represents a high-severity destructive action that could cause significant service disruption if invoked by an AI agent without proper authorization or understanding of consequences.

From the tool's definition Tool description explicitly states: 'Deletes a Fabric connection. This action cannot be undone and will terminate the connection.' The phrases 'cannot be undone' and 'delete' are definitive markers of destructive operations.

Questions about delete_connection

What does the delete_connection tool do? +

Deletes a Fabric connection. This action cannot be undone and will terminate the connection. It is categorised as a Destructive tool in the Equinix Fabric MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_connection? +

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

delete_connection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_connection? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.