disable_stream · Nginx Proxy Manager MCP: Risk & Policy

WHAT IT DOES

What disable_stream does on Nginx Proxy Manager MCP

AI agents use disable_stream 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 disable_stream needs a policy

This tool modifies state (disables a stream) in a network infrastructure component, which is reversible and can be re-enabled. While not destructive, disabling active streams can disrupt traffic routing and services that depend on those streams, giving it high severity due to potential blast radius in production proxy infrastructure. Write category is most appropriate as it modifies configuration state reversibly.

From the tool's definition Tool name 'disable_stream' combined with server context shows modification of Nginx Proxy Manager stream configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_stream Rate-limited

disable_stream 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": {
    "disable_stream": {
      "limits": [
        {
          "counter": "disable_stream_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 disable_stream

What does the disable_stream tool do? +

Disable a stream. 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 disable_stream? +

Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for disable_stream: 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 disable_stream? +

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

Can I rate-limit disable_stream? +

Yes. Add a rate_limit block to the disable_stream 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 disable_stream completely? +

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

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