This record as markdown: /tools/kiln/start-print.md
What start_print does on Kiln
AI agents invoke start_print to trigger actions in Kiln. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why start_print is rated High
This tool triggers an irreversible physical operation (heating, material extrusion, moving mechanical components). While not destructive of data, it commits real-world resources (materials, time, energy) and could cause equipment damage, fire hazards, or waste if misused.
From the tool's definition Tool named 'start_print' in a 3D printer control server (Kiln/OctoPrint/Moonraker/Bambu/Prusa/Elegoo context). Starts a physical print operation — an external action whose effects depend on which file/design is queued.
Attacks that exploit this kind of access
The rule that runs start_print 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 start_print, this is the rule to start with:
start_print stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 start_print call is checked against it from then on.
Questions about start_print
start_print is a execute tool on the Kiln MCP server. It is categorised as a Execute tool in the Kiln MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kiln MCP server in PolicyLayer and add a rule for start_print: 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.
start_print is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_print 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 start_print. 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.
start_print 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