Delete a redirection host by ID
AI agents call delete_redirection_host to permanently remove resources in Nginx Proxy Manager MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a redirection host is an irreversible action that destroys existing proxy configuration. Once deleted, the redirection host cannot be recovered without manual reconfiguration. This fits the Destructive category as it removes data that cannot be undone.
From the tool's definition Tool name contains 'delete' and description states 'Delete a redirection host by ID'. This performs an irreversible deletion operation on proxy infrastructure configuration.
Attacks that exploit this kind of access
Delete a redirection host by ID. It is categorised as a Destructive tool in the Nginx Proxy Manager MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for delete_redirection_host: 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 Nginx Proxy Manager MCP. Nothing to install.
delete_redirection_host 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_redirection_host 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_redirection_host. 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_redirection_host is provided by the Nginx Proxy Manager MCP server (verybigsad/nginx-proxy-manager-mcp). 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 →