This record as markdown: /tools/kiln/remove-spool.md
What remove_spool does on Kiln
AI agents call remove_spool 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 remove_spool is rated Critical
Removing a spool from inventory is a destructive operation that deletes or purges a record from the filament inventory. This is likely irreversible (the spool entry is gone), making it Destructive. The blast radius is medium since it affects inventory tracking data but does not directly damage physical hardware or financial systems.
From the tool's definition 'Remove a filament spool from inventory' — permanently removes an inventory record
Attacks that exploit this kind of access
The rule that runs remove_spool 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 remove_spool, this is the rule to start with:
remove_spool 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 remove_spool call is checked against it from then on.
Questions about remove_spool
Remove a filament spool from inventory. 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 remove_spool: 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.
remove_spool 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 remove_spool 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 remove_spool. 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.
remove_spool 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