Revenue breakdown by product.
AI agents call revenue_by_product to retrieve information from AdminAgent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays revenue analytics data broken down by product. It is a read-only reporting/query operation with no side effects. Misuse potential is minimal as it only exposes financial reporting data rather than executing transactions.
From the tool's definition Revenue breakdown by product
Attacks that exploit this kind of access
Revenue breakdown by product. It is categorised as a Read tool in the AdminAgent MCP Server, which means it retrieves data without modifying state.
Register the AdminAgent MCP server in PolicyLayer and add a rule for revenue_by_product: 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 AdminAgent. Nothing to install.
revenue_by_product 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 revenue_by_product 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 revenue_by_product. 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.
revenue_by_product is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). 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 →