This record as markdown: /tools/kiln/validate-gcode.md
What validate_gcode does on Kiln
AI agents invoke validate_gcode 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 validate_gcode is rated High
GCode validation on a 3D printer control platform likely involves parsing or executing GCode instructions to check their validity, which could trigger printer movements or operations. Even if it only reads/parses GCode, the context of a printer control server with 273 tools and the ability to send commands makes Execute the most likely category.
From the tool's definition Tool name 'validate_gcode' on a 3D printer control server (OctoPrint, Moonraker, Bambu, Prusa, Elegoo). Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs validate_gcode 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 validate_gcode, this is the rule to start with:
validate_gcode 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 validate_gcode call is checked against it from then on.
Questions about validate_gcode
validate_gcode 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 validate_gcode: 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.
validate_gcode 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 validate_gcode 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 validate_gcode. 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.
validate_gcode 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