update_stream · Nginx Proxy Manager MCP: Risk & Policy

WHAT IT DOES

What update_stream does on Nginx Proxy Manager MCP

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

The tool modifies existing stream configurations, which are critical network infrastructure settings. While the operation is reversible (can be undone by reverting the configuration), a stream update could redirect TCP/UDP traffic to malicious endpoints, alter load-balancing behavior, or compromise traffic flow.

From the tool's definition Tool performs 'Update an existing stream' — a reversible modification operation on stream configuration in Nginx Proxy Manager. Classified as Write rather than Execute because it modifies configuration state rather than triggering arbitrary code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_stream Rate-limited

update_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": {
    "update_stream": {
      "limits": [
        {
          "counter": "update_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 update_stream

What does the update_stream tool do? +

Update an existing 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 update_stream? +

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

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

Can I rate-limit update_stream? +

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

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

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