Get a specific user by ID
AI agents call get_user to retrieve information from Nginx Proxy Manager MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information by ID without creating, modifying, or deleting data. It is a straightforward query operation that poses minimal risk if misused—an agent could retrieve user details, but cannot modify infrastructure or cause harm through read access alone. Severity is low because exposure of user metadata is generally lower-impact than modification or deletion capabilities.
From the tool's definition Tool name is 'get_user' with description 'Get a specific user by ID' — the verb 'Get' and lack of modification language indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a specific user by ID. It is categorised as a Read tool in the Nginx Proxy Manager MCP MCP Server, which means it retrieves data without modifying state.
Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for get_user: 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.
get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user 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 get_user. 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.
get_user 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 →