This record as markdown: /tools/kiln/rollback-firmware.md
What rollback_firmware does on Kiln
AI agents call rollback_firmware to permanently remove resources in Kiln, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why rollback_firmware is rated Critical
Firmware rollback overwrites the current firmware on a physical device with an older version. This cannot be trivially undone (the current firmware is overwritten), could brick the printer or introduce known vulnerabilities, and constitutes an irreversible overwrite of system software.
From the tool's definition Tool name 'rollback_firmware' implies overwriting device firmware with a previous version — an irreversible modification to printer firmware state
Attacks that exploit this kind of access
The rule that runs rollback_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 rollback_firmware, this is the rule to start with:
rollback_firmware is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every rollback_firmware call is checked against it from then on.
Questions about rollback_firmware
rollback_firmware is a destructive tool on the Kiln MCP server. It is categorised as a Destructive tool in the Kiln MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kiln MCP server in PolicyLayer and add a rule for rollback_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.
rollback_firmware is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rollback_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 rollback_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.
rollback_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.
Across the catalogue