Delete an endpoint permanently
AI agents call delete_endpoint to permanently remove resources in GASSAPI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes API endpoint definitions from the system. The word 'permanently' confirms the deletion cannot be undone. While not as critical as deleting production data or financial records, the permanent loss of endpoint configurations could disrupt development workflows, break dependent integrations, and require manual recreation.
From the tool's definition Tool name 'delete_endpoint' combined with description 'Delete an endpoint permanently' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete an endpoint permanently. It is categorised as a Destructive tool in the GASSAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GASSAPI MCP Server MCP server in PolicyLayer and add a rule for delete_endpoint: 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 GASSAPI MCP Server. Nothing to install.
delete_endpoint 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 delete_endpoint 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 delete_endpoint. 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.
delete_endpoint is provided by the GASSAPI MCP Server MCP server (martin-1103/mcp2). 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 →