AI agents call get_open_positions 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 data about open positions without modifying state. It performs a query/list operation with no side effects, fitting the Read category. Severity is low because exposure of position data alone does not enable destructive or financial actions—it merely reveals information an authenticated user already has access to.
From the tool's definition Tool name 'get_open_positions' and server description states 'Read-only MCP server' that gives access to 'positions'. The description 'List the authenticated user' is minimally informative but consistent with a read operation that retrieves user position data.
Attacks that exploit this kind of access
List 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_open_positions: 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_open_positions 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_open_positions 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_open_positions. 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_open_positions 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 →