Get current user
AI agents call get-user-info to retrieve information from NeoDB 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 from NeoDB, a read-only operation with no ability to modify, delete, or execute actions. The data returned is limited to the authenticated user's own profile information. Severity is low because exposure of a single user's public/semi-public profile data on a book cataloging service has minimal security impact.
From the tool's definition Tool name 'get-user-info' and description 'Get current user' indicate a retrieval operation that fetches user profile data without modification or side effects.
Attacks that exploit this kind of access
Get current user. It is categorised as a Read tool in the NeoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NeoDB MCP Server MCP server in PolicyLayer and add a rule for get-user-info: 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 NeoDB MCP Server. Nothing to install.
get-user-info 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-info 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-info. 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-info is provided by the NeoDB MCP Server MCP server (xytangme/neodb-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 →