This record as markdown: /tools/kiln/cancel-print-recovery.md
What cancel_print_recovery does on Kiln
AI agents call cancel_print_recovery 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 cancel_print_recovery is rated Critical
Cancelling a recovery session permanently ends it; there is no indication this can be reversed or re-initiated from the same state. In the context of 3D printing, aborting a recovery mid-process could result in a failed print and wasted material. This is more severe than a simple Write operation because the session state is lost irreversibly.
From the tool's definition 'Cancel an active recovery session' — cancelling a recovery session is an irreversible action that terminates an ongoing recovery process, which cannot be undone
Attacks that exploit this kind of access
The rule that runs cancel_print_recovery 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 cancel_print_recovery, this is the rule to start with:
cancel_print_recovery 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 cancel_print_recovery call is checked against it from then on.
Questions about cancel_print_recovery
Cancel an active recovery session. 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 cancel_print_recovery: 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.
cancel_print_recovery 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 cancel_print_recovery 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 cancel_print_recovery. 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.
cancel_print_recovery 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