Delete a redirection host.
AI agents call npm_delete_redirection_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.
Deletion operations are inherently destructive and irreversible. Removing a redirection host cannot be undone and would break routing for any traffic directed to that host. This action has direct operational impact on the nginx proxy infrastructure. The high severity reflects the potential blast radius: users/services relying on that redirection would lose connectivity.
From the tool's definition Tool name 'npm_delete_redirection_host' and description 'Delete a redirection host' indicate irreversible removal of a redirection host configuration.
Attacks that exploit this kind of access
Delete a redirection 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_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 Manager. Nothing to install.
npm_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 npm_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 npm_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.
npm_delete_redirection_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 →