AI agents call printer_stats 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 queries and returns historical statistics about printer usage. It performs a read-only operation with no capability to modify printer state, execute commands, delete data, or affect financial systems. The only information exposed is aggregated usage metrics that do not enable harmful actions. Severity is low because misuse would at most reveal benign operational metrics.
From the tool's definition Tool name 'printer_stats' and description 'Get aggregate statistics for a printer: total prints, success rate, average duration' — uses action verb 'Get' which retrieves data without modification or side effects.
Attacks that exploit this kind of access
Get aggregate statistics for a printer: total prints, success rate, average duration. 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 printer_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 Kiln. Nothing to install.
printer_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 printer_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 printer_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.
printer_stats 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 →