This record as markdown: /tools/kiln/pipeline-resume.md
What pipeline_resume does on Kiln
AI agents invoke pipeline_resume 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.
Why pipeline_resume is rated High
This tool triggers execution of an ongoing 3D printing pipeline by resuming a paused process. It initiates external physical operations (3D printer activity), making it an Execute-category tool. Misuse could cause unintended printer operation, wasted material, or equipment issues.
From the tool's definition Resume a paused pipeline from where it stopped
Attacks that exploit this kind of access
The rule that runs pipeline_resume 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 pipeline_resume, this is the rule to start with:
pipeline_resume stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every pipeline_resume call is checked against it from then on.
Questions about pipeline_resume
Resume a paused pipeline from where it stopped. 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 pipeline_resume: 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.
pipeline_resume 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 pipeline_resume 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 pipeline_resume. 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.
pipeline_resume 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.
This server
Across the catalogue