This record as markdown: /tools/kiln/validate-openscad-code.md
What validate_openscad_code does on Kiln
AI agents invoke validate_openscad_code 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_openscad_code is rated High
Validating OpenSCAD code likely involves executing or interpreting the code in a sandbox to check for errors, which constitutes code execution. Given the server controls 3D printers, misuse could trigger unintended printer operations. Confidence is reduced due to empty description — it may be purely static analysis (Read), but execution is the more conservative and likely interpretation.
From the tool's definition Tool name 'validate_openscad_code' implies running/parsing OpenSCAD code; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs validate_openscad_code 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_openscad_code, this is the rule to start with:
validate_openscad_code 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_openscad_code call is checked against it from then on.
Questions about validate_openscad_code
validate_openscad_code 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_openscad_code: 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_openscad_code 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_openscad_code 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_openscad_code. 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_openscad_code 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