This record as markdown: /tools/kiln/pipeline-retry-step.md
What pipeline_retry_step does on Kiln
AI agents invoke pipeline_retry_step 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_retry_step is rated High
The name implies triggering re-execution of a pipeline step, which is an Execute-class action (running/triggering an operation). However, with no description, confidence is low. Given the server context (3D printer control), retrying a pipeline step could affect ongoing print jobs. Severity is medium due to potential impact on physical hardware operations.
From the tool's definition Tool name 'pipeline_retry_step' suggests re-executing a step in a pipeline; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs pipeline_retry_step 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_retry_step, this is the rule to start with:
pipeline_retry_step 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_retry_step call is checked against it from then on.
Questions about pipeline_retry_step
pipeline_retry_step is a execute tool on the Kiln MCP server. 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_retry_step: 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_retry_step 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_retry_step 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_retry_step. 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_retry_step 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