ID\
AI agents call get_user_by_id to retrieve information from MCP JSON Database Server 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 identifier with no indication of modification, deletion, or code execution. It has no side effects beyond querying data. While it may expose user information (which could have privacy implications), that does not change the functional category—it remains a Read operation.
From the tool's definition Tool name 'get_user_by_id' indicates a retrieval operation. The server description mentions 'secure CRUD operations' where read operations retrieve data.
Attacks that exploit this kind of access
ID\. It is categorised as a Read tool in the MCP JSON Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP JSON Database Server 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 JSON Database Server. 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 JSON Database Server MCP server (yusuferenkt/mcp-database). 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 →