AI agents invoke start_print_recovery 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.
This tool triggers execution of a recovery plan on 3D printer hardware, which constitutes an Execute action. Recovery plans can involve thermal adjustments, mechanical movements, or resumption of partially-failed prints, all of which are irreversible physical operations. The high severity reflects potential for damage to in-progress prints, hardware stress, or material waste if a malformed recovery plan is executed.
From the tool's definition Tool name 'start_print_recovery' and description 'Begin executing a recovery plan' indicate initiation of automated operations on 3D printer hardware.
Attacks that exploit this kind of access
Begin executing a recovery plan. 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 start_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.
start_print_recovery 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 start_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 start_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.
start_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →