This record as markdown: /tools/kiln/generate-and-print.md
What generate_and_print does on Kiln
AI agents invoke generate_and_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 generate_and_print is rated High
The name 'generate_and_print' strongly implies triggering a physical 3D print job — an external real-world operation involving hardware actuation, material consumption, and potentially extended machine operation. This fits the Execute category (triggering external operations). Severity is high because misuse could waste materials, damage hardware, or run unintended prints.
From the tool's definition Tool name 'generate_and_print' on a server described as 'AI agent control of 3D printers' with tools for OctoPrint, Moonraker, Bambu, Prusa, Elegoo.
Attacks that exploit this kind of access
The rule that runs generate_and_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 generate_and_print, this is the rule to start with:
generate_and_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 generate_and_print call is checked against it from then on.
Questions about generate_and_print
generate_and_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 generate_and_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.
generate_and_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 generate_and_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 generate_and_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.
generate_and_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