Cancel all pending/in-progress parts of a split plan.
AI agents call cancel_split_plan 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.
Cancelling a split print plan terminates in-progress 3D printing operations, which cannot be undone. The partially-printed parts are lost, wasted material results, and the manufacturing state cannot be recovered. This is irreversible destruction of an active process. While not data deletion, it is destructive of work-in-progress with significant impact (material waste, time loss, failed prints).
From the tool's definition Tool name 'cancel_split_plan' combined with description 'Cancel all pending/in-progress parts of a split plan' indicates irreversible termination of print job(s).
Attacks that exploit this kind of access
Cancel all pending/in-progress parts of a split plan. 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_split_plan: 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_split_plan 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_split_plan 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_split_plan. 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_split_plan 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 →