This record as markdown: /tools/kiln/insert-into-scad.md
What insert_into_scad does on Kiln
AI agents invoke insert_into_scad 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 insert_into_scad is rated High
OpenSCAD is a script-based 3D modeling language. Inserting into a SCAD script implies writing or executing code that could be used to generate or modify 3D models. Given the context of a 3D printer control server, this likely involves writing/executing script content. With no description available, confidence is reduced, but the name suggests at minimum a Write action and potentially Execute if the script is run.
From the tool's definition Tool name 'insert_into_scad' suggests executing or modifying OpenSCAD code/scripts; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs insert_into_scad 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 insert_into_scad, this is the rule to start with:
insert_into_scad 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 insert_into_scad call is checked against it from then on.
Questions about insert_into_scad
insert_into_scad 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 insert_into_scad: 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.
insert_into_scad 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 insert_into_scad 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 insert_into_scad. 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.
insert_into_scad 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