Delete a specific connection endpoint.
AI agents call deleteConnectionsByEndpoint 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.
This tool performs an irreversible deletion operation on connection endpoints. Even though the scope is limited to a specific endpoint rather than bulk data, the permanent removal of a connection endpoint could disrupt system operations and cannot be undone. This warrants a 'Destructive' category with high severity due to the potential impact on system connectivity and the irreversible nature of the operation.
From the tool's definition Tool name is 'deleteConnectionsByEndpoint' and description states 'Delete a specific connection endpoint.' The verb 'Delete' combined with the action of removing a connection endpoint indicates irreversible data deletion.
Attacks that exploit this kind of access
Delete a specific connection endpoint. 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 deleteConnectionsByEndpoint: 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.
deleteConnectionsByEndpoint 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 deleteConnectionsByEndpoint 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 deleteConnectionsByEndpoint. 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.
deleteConnectionsByEndpoint 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.
deleteConnectionsByEndpoint is one line of Xdevplatform/x's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →