Delete a URL redirect by its ID. This action is irreversible. Use cases: - Remove duplicate or outdated redirects - Clean up test data - Remove redirects that were incorrectly created
AI agents call delete_redirect to permanently remove resources in Pulsemcp Cms Admin — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a URL redirect from the system without ability to undo the action. The description explicitly states 'irreversible', which is a defining characteristic of destructive operations.
From the tool's definition Delete a URL redirect by its ID. This action is irreversible.
Attacks that exploit this kind of access
Delete a URL redirect by its ID. This action is irreversible. Use cases: - Remove duplicate or outdated redirects - Clean up test data - Remove redirects that were incorrectly created. It is categorised as a Destructive tool in the Pulsemcp Cms Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pulsemcp Cms Admin MCP server in PolicyLayer and add a rule for delete_redirect: 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 Pulsemcp Cms Admin. Nothing to install.
delete_redirect 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_redirect 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_redirect. 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_redirect is provided by the Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-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 →