Disable a proxy host
AI agents use disable_proxy_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.
This tool modifies the operational state of a proxy host by disabling it, which is a Write operation—reversible configuration change. While disabling a proxy host could have significant business impact (service disruption), the action itself is not destructive or financial.
From the tool's definition Tool name 'disable_proxy_host' and description 'Disable a proxy host' indicate a state-modifying operation on proxy infrastructure. The action is reversible (can be re-enabled), distinguishing it from deletion.
Attacks that exploit this kind of access
Disable a proxy 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.
Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for disable_proxy_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.
disable_proxy_host is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_proxy_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 disable_proxy_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.
disable_proxy_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 →