npm_set_user_permissions · Nginx Manager MCP: Risk & Policy

WHAT IT DOES

What npm_set_user_permissions does on Nginx Manager

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

WHY IT NEEDS A POLICY

Why npm_set_user_permissions needs a policy

The tool modifies user permissions, which is a state change but reversible. While permissions changes could have security implications if abused (e.g., granting admin access), the impact is limited to the Nginx Proxy Manager's access control model and does not involve financial transactions, code execution, or permanent destruction.

From the tool's definition Tool name 'npm_set_user_permissions' and description 'Set a user' indicate modification of user configuration/permissions without deletion. This is a reversible create-or-update operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

npm_set_user_permissions Rate-limited

npm_set_user_permissions 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": {
    "npm_set_user_permissions": {
      "limits": [
        {
          "counter": "npm_set_user_permissions_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 Manager, so you can run agents against it safely.

FAQ

Questions about npm_set_user_permissions

What does the npm_set_user_permissions tool do? +

Set a user. It is categorised as a Write tool in the Nginx Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on npm_set_user_permissions? +

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

What risk level is npm_set_user_permissions? +

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

Can I rate-limit npm_set_user_permissions? +

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

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

npm_set_user_permissions is provided by the Nginx Manager MCP server (kognar-ai/ngnix-manager-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.