// SCAN REPORT

Nginx Manager

54 tools. 34 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

34 can modify or destroy data

20 read-only

54 tools total

Community server · catalogue entry verified 30/06/2026

How to control Nginx Manager ↓

TOOL MAP

What Nginx Manager exposes to your agents

Read (20) Write / Execute (27) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Nginx Manager tools

Destructive · High npm_delete_access_list This tool permanently deletes access list configurations from Nginx Proxy Manager. Destructive · High npm_delete_certificate Deleting a certificate is a destructive action that cannot be undone. Destructive · High npm_delete_dead_host This tool permanently removes a dead host (404 host) configuration from Nginx Proxy Manager. Destructive · High npm_delete_proxy_host Deletion of infrastructure configuration (proxy hosts) cannot be undone and causes permanent loss of the proxy routing setup.

34 of Nginx Manager's 54 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Nginx Manager

PolicyLayer is an MCP gateway — it sits between your AI agents and Nginx Manager, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "npm_delete_access_list": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "npm_create_access_list": {
    "limits": [
      {
        "counter": "npm_create_access_list_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "npm_get_access_list": {
    "limits": [
      {
        "counter": "npm_get_access_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Nginx Manager — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NGINX MANAGER →

Instant setup, no code required.

FULL CATALOGUE

All 54 Nginx Manager tools

DESTRUCTIVE 7 tools

Destructive npm_delete_access_list Delete an access list. Destructive npm_delete_certificate Delete a certificate by ID. Destructive npm_delete_dead_host Delete a 404 host. Destructive npm_delete_proxy_host Delete a proxy host by ID. Destructive npm_delete_redirection_host Delete a redirection host. Destructive npm_delete_stream Delete a stream. Destructive npm_delete_user Delete a user.

EXECUTE 2 tools

Execute npm_renew_certificate Renew a Let Execute npm_test_certificate_http_reach Test whether domains are HTTP-reachable before requesting a cert.

WRITE 25 tools

Write npm_create_access_list Create an access list. Write npm_create_certificate_custom Create a custom certificate record. File upload must follow via npm_upload_certificate. Write npm_create_certificate_letsencrypt Request a new Let Write npm_create_dead_host Create a 404 host. Write npm_create_proxy_host Create a new proxy host. Write npm_create_redirection_host Create a redirection host. Write npm_create_stream Create a TCP/UDP stream. Write npm_create_user Create a new user. Write npm_disable_dead_host Disable a 404 host. Write npm_disable_proxy_host Disable a proxy host. Write npm_disable_redirection_host Disable a redirection host. Write npm_disable_stream Disable a stream. Write npm_enable_dead_host Enable a 404 host. Write npm_enable_proxy_host Enable a proxy host. Write npm_enable_redirection_host Enable a redirection host. Write npm_enable_stream Enable a stream. Write npm_set_user_password Set a user Write npm_set_user_permissions Set a user Write npm_update_access_list Update an access list. Write npm_update_dead_host Update a 404 host. Write npm_update_proxy_host Update an existing proxy host (partial fields allowed). Write npm_update_redirection_host Update a redirection host. Write npm_update_setting Update a setting by name. Write npm_update_stream Update a stream. Write npm_update_user Update a user.

READ 20 tools

Read npm_get_access_list Get an access list by ID. Read npm_get_audit_log Fetch the audit log. Read npm_get_certificate Get a certificate by ID. Read npm_get_dead_host Get a 404 host by ID. Read npm_get_me Get the currently authenticated user. Read npm_get_proxy_host Get a proxy host by ID. Read npm_get_redirection_host Get a redirection host by ID. Read npm_get_reports_hosts Aggregate hosts report (counts by type/status). Read npm_get_setting Get a setting by name. Read npm_get_settings List all NPM settings. Read npm_get_stream Get a stream by ID. Read npm_get_user Get a user by ID. Pass Read npm_health Check NPM API health/version. Read npm_list_access_lists List all access lists. Read npm_list_certificates List all SSL certificates. Read npm_list_dead_hosts List all 404 (dead) hosts. Read npm_list_proxy_hosts List all proxy hosts configured in Nginx Proxy Manager. Read npm_list_redirection_hosts List all redirection hosts. Read npm_list_streams List all TCP/UDP streams. Read npm_list_users List all NPM users.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Nginx Manager

Can an AI agent delete data through the Nginx Manager MCP server? +

Yes. The Nginx Manager server exposes 7 destructive tools including npm_delete_access_list, npm_delete_certificate, npm_delete_dead_host. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Nginx Manager? +

The Nginx Manager server has 25 write tools including npm_create_access_list, npm_create_certificate_custom, npm_create_certificate_letsencrypt. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Nginx Manager.

How many tools does the Nginx Manager MCP server expose? +

54 tools across 3 categories: Destructive, Read, Write. 20 are read-only. 34 can modify, create, or delete data.

How do I enforce a policy on Nginx Manager? +

Register the Nginx Manager MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Nginx Manager tool call.

Deterministic rules across all 54 Nginx Manager tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NGINX MANAGER →

Instant setup, no code required.

54 Nginx Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.