Get a specific user by their ID
AI agents call get_user_by_id to retrieve information from MCP Node Js TypeScript API 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 side effects. It is a read-only query operation that poses minimal risk if misused by an AI agent—the worst outcome is unauthorized information disclosure of an existing user record, not data modification or deletion. The low severity reflects that this is a standard retrieval operation.
From the tool's definition Tool name 'get_user_by_id' and description 'Get a specific user by their ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a specific user by their ID. It is categorised as a Read tool in the MCP Node Js TypeScript API MCP Server, which means it retrieves data without modifying state.
Register the MCP Node Js TypeScript API MCP server in PolicyLayer and add a rule for get_user_by_id: 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 MCP Node Js TypeScript API. Nothing to install.
get_user_by_id 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_by_id 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_by_id. 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_by_id is provided by the MCP Node Js TypeScript API MCP server (proffillipesilva/mcpnodefil). 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 →