This record as markdown: /tools/kiln/design-to-gcode-pipeline.md
What design_to_gcode_pipeline does on Kiln
AI agents invoke design_to_gcode_pipeline 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 design_to_gcode_pipeline is rated High
The name implies execution of a pipeline (a sequence of automated steps) to produce G-code — the instruction set sent directly to 3D printer hardware. Misuse could result in incorrect G-code being generated and sent to a printer, potentially causing hardware damage or print failures. The description is empty, which lowers confidence.
From the tool's definition Tool name 'design_to_gcode_pipeline' suggests a multi-step pipeline converting a design into G-code, which involves executing a processing/compilation workflow that generates machine control instructions for 3D printers.
Attacks that exploit this kind of access
The rule that runs design_to_gcode_pipeline 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 design_to_gcode_pipeline, this is the rule to start with:
design_to_gcode_pipeline 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 design_to_gcode_pipeline call is checked against it from then on.
Questions about design_to_gcode_pipeline
design_to_gcode_pipeline 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 design_to_gcode_pipeline: 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.
design_to_gcode_pipeline 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 design_to_gcode_pipeline 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 design_to_gcode_pipeline. 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.
design_to_gcode_pipeline 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