This record as markdown: /tools/kiln/smart-reprint.md
What smart_reprint does on Kiln
AI agents invoke smart_reprint 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 smart_reprint is rated High
Given the server context (controlling 3D printers via OctoPrint, Moonraker, Bambu, Prusa, Elegoo), 'smart_reprint' most likely triggers a reprint job on a physical 3D printer, which is an external operation with real-world effects (material consumption, hardware operation, potential safety implications). This maps to Execute.
From the tool's definition Tool name 'smart_reprint' on a 3D printer control server (Kiln — AI agent control of 3D printers). Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs smart_reprint 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 smart_reprint, this is the rule to start with:
smart_reprint 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 smart_reprint call is checked against it from then on.
Questions about smart_reprint
smart_reprint 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 smart_reprint: 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.
smart_reprint 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 smart_reprint 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 smart_reprint. 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.
smart_reprint 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