deleteConnectionsByUuids
Delete connections by their unique identifiers.
This record as markdown: /tools/xdevplatform-xmcp/deleteconnectionsbyuuids.md
What deleteConnectionsByUuids does on Xdevplatform/xmcp
AI agents call deleteConnectionsByUuids to permanently remove resources in Xdevplatform/xmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteConnectionsByUuids is rated Critical
This tool permanently removes data (connections) identified by UUIDs. Deletion is irreversible and cannot be undone, fitting the Destructive category definition. The high severity reflects that an agent misusing this could permanently remove user connections without recovery. Confidence is high due to explicit 'delete' language in both name and description, despite the server lacking a description.
From the tool's definition Tool name 'deleteConnectionsByUuids' explicitly performs deletion by identifiers. Description states 'Delete connections' which is an irreversible operation.
Attacks that exploit this kind of access
The rule that runs deleteConnectionsByUuids safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteConnectionsByUuids, this is the rule to start with:
deleteConnectionsByUuids is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every deleteConnectionsByUuids call is checked against it from then on.
Questions about deleteConnectionsByUuids
Delete connections by their unique identifiers. It is categorised as a Destructive tool in the Xdevplatform/xmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for deleteConnectionsByUuids: 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 Xdevplatform/xmcp. Nothing to install.
deleteConnectionsByUuids 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 deleteConnectionsByUuids 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 deleteConnectionsByUuids. 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.
deleteConnectionsByUuids is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xdevplatform/x, and thousands of servers like it.
Across the catalogue