AI agents call get_account_summary to retrieve information from Mcp Pear without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account summary information about the authenticated user. It performs a read-only query returning existing data without modifying, deleting, or executing any operations. The low severity reflects minimal blast radius—misuse would only expose user account information already accessible to the authenticated session.
From the tool's definition Tool description states 'Get the authenticated user' and server is explicitly described as 'Read-only MCP server'. This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the authenticated user. It is categorised as a Read tool in the Mcp Pear MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pear MCP server in PolicyLayer and add a rule for get_account_summary: 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 Pear. Nothing to install.
get_account_summary 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_account_summary 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_account_summary. 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_account_summary is provided by the Mcp Pear MCP server (marvelnwachukwu/mcp-pear). 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 →