Delete a 404 host.
AI agents call npm_delete_dead_host to permanently remove resources in Nginx Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a dead host (404 host) configuration from Nginx Proxy Manager. Deletion of infrastructure configurations cannot be undone and represents an irreversible action. While the blast radius is scoped to a single host rather than the entire system, deletion of proxy configurations could disrupt traffic routing and cause service interruptions.
From the tool's definition Tool name includes 'delete' and description states 'Delete a 404 host.' The operation removes a host configuration irreversibly.
Attacks that exploit this kind of access
Delete a 404 host. It is categorised as a Destructive tool in the Nginx Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nginx Manager MCP server in PolicyLayer and add a rule for npm_delete_dead_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 Manager. Nothing to install.
npm_delete_dead_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 npm_delete_dead_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 npm_delete_dead_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.
npm_delete_dead_host is provided by the Nginx Manager MCP server (kognar-ai/ngnix-manager-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 →