AI agents call revenue_dashboard to retrieve information from Kiln 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 aggregate revenue analytics data without modifying, executing actions, or affecting financial transactions. It is a read operation that queries existing financial analytics rather than moving money or committing financial obligations. While it involves financial data, the Financial category applies to tools that move money or create obligations; this tool only reads analytics.
From the tool's definition Tool name 'revenue_dashboard' and description 'Get aggregate revenue analytics dashboard' indicate a data retrieval operation with no side effects. The verb 'Get' and 'dashboard' query pattern are characteristic of read-only analytics access.
Attacks that exploit this kind of access
Get aggregate revenue analytics dashboard. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for revenue_dashboard: 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 Kiln. Nothing to install.
revenue_dashboard 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_dashboard 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_dashboard. 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_dashboard is provided by the Kiln MCP server (codeofaxel/Kiln). 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 →