Get user information
AI agents call get_user to retrieve information from MemoDB MCP 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 without altering, deleting, or executing actions. It is a straightforward query operation that falls clearly under the Read category. Severity is low because user information retrieval poses minimal risk unless the data itself is highly sensitive, but the tool performs no destructive or harmful actions. Confidence is high due to clear naming and description.
From the tool's definition Tool name 'get_user' and description 'Get user information' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get user information. It is categorised as a Read tool in the MemoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MemoDB 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 MemoDB 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 MemoDB MCP Server MCP server (wuyunmei/momedb-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 →