create_dead_host · Nginx Proxy Manager MCP: Risk & Policy

WHAT IT DOES

What create_dead_host does on Nginx Proxy Manager MCP

AI agents use create_dead_host to create or update resources in Nginx Proxy Manager MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nginx Proxy Manager MCP environment.

WHY IT NEEDS A POLICY

Why create_dead_host needs a policy

This tool creates a new proxy host configuration that is irreversible only through deletion, making it a Write operation rather than Destructive. The severity is medium because misconfiguration could block legitimate traffic or disrupt service availability, affecting users trying to access services through the proxy.

From the tool's definition Tool name is 'create_dead_host' and description states 'Create a new 404 dead host'. This creates a new configuration entry in Nginx Proxy Manager that returns 404 responses.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dead_host Rate-limited

create_dead_host stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dead_host": {
      "limits": [
        {
          "counter": "create_dead_host_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nginx Proxy Manager MCP, so you can run agents against it safely.

FAQ

Questions about create_dead_host

What does the create_dead_host tool do? +

Create a new 404 dead host. It is categorised as a Write tool in the Nginx Proxy Manager MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_dead_host? +

Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for create_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 Proxy Manager MCP. Nothing to install.

What risk level is create_dead_host? +

create_dead_host is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_dead_host? +

Yes. Add a rate_limit block to the create_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.

How do I block create_dead_host completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_dead_host? +

create_dead_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.