Delete a connection. Returns 409 if it has active rules unless force_delete is true.
AI agents call meshes_delete_connection to permanently remove resources in Mesheshq — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes integration connections, which are foundational infrastructure components in the Meshes integration layer. Deletion is irreversible and could disrupt active workflows and integrations. The 'force_delete' parameter allowing bypass of safety checks (409 on active rules) amplifies the risk.
From the tool's definition Tool name 'meshes_delete_connection' and description 'Delete a connection' indicate irreversible deletion of data. The mention of 'force_delete' parameter confirms this is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a connection. Returns 409 if it has active rules unless force_delete is true. It is categorised as a Destructive tool in the Mesheshq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mesheshq MCP server in PolicyLayer and add a rule for meshes_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 Mesheshq. Nothing to install.
meshes_delete_connection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meshes_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.
Set action: deny in the PolicyLayer policy for meshes_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.
meshes_delete_connection is provided by the Mesheshq MCP server (mesheshq/meshes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →