AI agents call model_revenue 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 or queries revenue data for reporting/analytics purposes. Although it involves financial information, it performs no financial transactions, does not move money, and does not commit financial obligations. The verb 'Get' and 'summary' indicate read-only access. While the information is financial in nature, the action itself is data retrieval, making it a Read category tool.
From the tool's definition Tool name 'model_revenue' combined with description 'Get revenue summary' indicates a retrieval operation that queries existing financial data without modification or transaction execution.
Attacks that exploit this kind of access
Get revenue summary for a specific model. 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 model_revenue: 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.
model_revenue 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 model_revenue 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 model_revenue. 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.
model_revenue 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.
model_revenue is one line of Kiln's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →