Return information about the authenticated Google user (requires OAuth).
AI agents call get_user_info to retrieve information from MCP Beancount Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information from Google OAuth without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal: an agent could learn the authenticated user's identity and associated profile details, but cannot alter accounts, perform financial transactions, or execute code. This is a straightforward Read operation.
From the tool's definition Tool description states 'Return information about the authenticated Google user' — a retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
Return information about the authenticated Google user (requires OAuth). It is categorised as a Read tool in the MCP Beancount Tool MCP Server, which means it retrieves data without modifying state.
Register the MCP Beancount Tool 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 MCP Beancount Tool. 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 MCP Beancount Tool MCP server (onesvat/mcp-beancount). 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 →