Retrieve a user by email address
AI agents call get-user to retrieve information from MongoDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns user data based on an email parameter. It performs no side effects, modifications, or irreversible actions. The operation is limited to fetching existing records, making it a Read category tool with low severity since data exposure depends on the sensitivity of user records returned and access controls already in place on the MongoDB server.
From the tool's definition Tool description states 'Retrieve a user by email address' — a pure data retrieval operation with no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
Retrieve a user by email address. It is categorised as a Read tool in the MongoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MongoDB MCP Server 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 MongoDB MCP Server. 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 MongoDB MCP Server MCP server (jb-7-jay/learn-mcp-server-mongo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get-user is one line of MongoDB MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →