This record as markdown: /tools/kiln/update-firmware.md
What update_firmware does on Kiln
AI agents invoke update_firmware 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 update_firmware is rated High
Firmware updates modify the low-level software running on a physical 3D printer. This is an irreversible or difficult-to-reverse operation that executes a flash/write process on embedded hardware. Misuse could brick the printer or introduce malicious firmware. Classified as Execute (bordering on Destructive) given the potential for permanent hardware damage, but without a description confidence is moderate.
From the tool's definition Tool name 'update_firmware' on a 3D printer control server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs update_firmware 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 update_firmware, this is the rule to start with:
update_firmware 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 update_firmware call is checked against it from then on.
Questions about update_firmware
update_firmware 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 update_firmware: 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.
update_firmware 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 update_firmware 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 update_firmware. 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.
update_firmware 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