AI agents call print_history 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 historical data about completed prints. There are no indications it modifies printer configuration, executes print jobs, deletes records, or triggers hardware actions. It is purely informational retrieval, fitting the Read category. Severity is low because misuse (e.g., an agent repeatedly querying history) poses minimal risk to hardware, data integrity, or operations.
From the tool's definition Tool name and description indicate it 'Get[s] recent print history' — a retrieval operation with no side effects. The phrase 'success/failure tracking' suggests it queries existing data rather than modifying printer state or executing commands.
Attacks that exploit this kind of access
Get recent print history with success/failure tracking. 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 print_history: 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.
print_history 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 print_history 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 print_history. 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.
print_history 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 →