AI agents call printer_status 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.
Status queries retrieve current operational state without modifying, deleting, or executing external actions. While the description is empty, the name strongly indicates a simple query operation. Misuse risk is low—returning printer state cannot harm hardware or data. Confidence is high given the clear semantic meaning and sibling tools that include modifying actions (add_spool, activate_license) by contrast.
From the tool's definition Tool name 'printer_status' indicates retrieval of printer state/status information. Context shows this is part of a 3D printer control system (OctoPrint, Moonraker, Bambu, Prusa, Elegoo), where status queries are standard read-only monitoring operations.
Attacks that exploit this kind of access
printer_status. 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_status: 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_status 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_status 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_status. 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_status 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 →