This record as markdown: /tools/kiln/modify-scad-module.md
What modify_scad_module does on Kiln
AI agents use modify_scad_module to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why modify_scad_module is rated Medium
The tool modifies OpenSCAD modules (scad_module), which are reversible code/data changes. This is a Write operation rather than Execute because it manipulates design files rather than running/executing print jobs. It ranks above Read (creates/modifies data) but below Destructive (reversible).
From the tool's definition Tool name 'modify_scad_module' indicates modification of OpenSCAD module code. Empty description limits confidence but 'modify' clearly denotes a write operation on design files.
Attacks that exploit this kind of access
The rule that runs modify_scad_module 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 modify_scad_module, this is the rule to start with:
modify_scad_module stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 modify_scad_module call is checked against it from then on.
Questions about modify_scad_module
modify_scad_module is a write tool on the Kiln MCP server. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for modify_scad_module: 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.
modify_scad_module is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the modify_scad_module 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 modify_scad_module. 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.
modify_scad_module 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