Delete a shortened URL by its short code.
AI agents call delete_short_url to permanently remove resources in Mcp Shlink — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (short URL records) and cannot be undone. While the blast radius is not system-critical, deletion of URL mappings could disrupt services relying on those shortened links. This is categorized as Destructive rather than Write because the operation cannot be reversed—once deleted, the URL mapping is gone.
From the tool's definition Tool name is 'delete_short_url' and description states 'Delete a shortened URL by its short code.' The verb 'delete' and the action of removing a shortened URL indicate irreversible removal of data.
Attacks that exploit this kind of access
Delete a shortened URL by its short code. It is categorised as a Destructive tool in the Mcp Shlink MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Shlink MCP server in PolicyLayer and add a rule for delete_short_url: 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 Mcp Shlink. Nothing to install.
delete_short_url 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_short_url 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_short_url. 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_short_url is provided by the Mcp Shlink MCP server (magnus919/mcp-shlink). 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 →