Get your Pool revenue sharing earnings estimate for the current month. Shows per-package breakdown with installs, share %, and estimated earnings. Requires authentication.
AI agents call lpm_pool_stats to retrieve information from Lpm Registry without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves financial information (earnings estimates, install counts, revenue share percentages) but does not move money, create transactions, modify data, or execute arbitrary operations. It is purely informational—a financial data Read operation. The 'Requires authentication' clause confirms it accesses user-specific data but maintains read-only semantics.
From the tool's definition Tool description explicitly states 'Get your Pool revenue sharing earnings estimate' and 'Shows per-package breakdown' — retrieves and displays financial data without modifying it. The word 'Get' and 'Shows' indicate read-only operations.
Attacks that exploit this kind of access
Get your Pool revenue sharing earnings estimate for the current month. Shows per-package breakdown with installs, share %, and estimated earnings. Requires authentication. It is categorised as a Read tool in the Lpm Registry MCP Server, which means it retrieves data without modifying state.
Register the Lpm Registry MCP server in PolicyLayer and add a rule for lpm_pool_stats: 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 Lpm Registry. Nothing to install.
lpm_pool_stats 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 lpm_pool_stats 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 lpm_pool_stats. 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.
lpm_pool_stats is provided by the Lpm Registry MCP server (lpm-dev/mcp-server). 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 →