This record as markdown: /tools/kiln/print-status-lite.md
What print_status_lite does on Kiln
AI agents call print_status_lite to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why print_status_lite is rated Low
Based on naming convention, this tool retrieves current printer status (a read operation with no side effects). The absence of verbs like 'start', 'stop', 'delete', or 'modify', combined with the '_lite' suffix implying a query variant, strongly indicates a Read operation. In the context of 3D printer control systems, status queries are typically non-destructive information retrieval.
From the tool's definition Tool name 'print_status_lite' suggests querying printer status without modification; 'lite' variant indicates a lightweight read operation. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
The rule that runs print_status_lite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For print_status_lite, this is the rule to start with:
print_status_lite is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every print_status_lite call is checked against it from then on.
Questions about print_status_lite
print_status_lite is a read tool on the Kiln MCP server. 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_status_lite: 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_status_lite 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_status_lite 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_status_lite. 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_status_lite 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.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue