This record as markdown: /tools/kiln/rollback-design-version.md
What rollback_design_version does on Kiln
AI agents call rollback_design_version 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_design_version is rated Critical
The term 'rollback' implies reverting to a previous design version, which typically overwrites the current state irreversibly. In the context of 3D printer design management, rolling back could discard current work permanently. However, the description is empty, so confidence is reduced.
From the tool's definition Tool name 'rollback_design_version' — no description provided
Attacks that exploit this kind of access
The rule that runs rollback_design_version 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_design_version, this is the rule to start with:
rollback_design_version 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_design_version call is checked against it from then on.
Questions about rollback_design_version
rollback_design_version 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_design_version: 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_design_version 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_design_version 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_design_version. 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_design_version 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