This record as markdown: /tools/kiln/troubleshoot-printer.md
What troubleshoot_printer does on Kiln
AI agents invoke troubleshoot_printer 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 troubleshoot_printer is rated High
Troubleshooting a 3D printer likely involves executing diagnostic commands, resetting states, or triggering operations on physical hardware. Given the server context (OctoPrint, Moonraker, Bambu, Prusa, Elegoo control), this tool could interact with the printer in ways that affect ongoing prints or hardware state.
From the tool's definition Tool name 'troubleshoot_printer' on a server controlling 3D printers; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs troubleshoot_printer 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 troubleshoot_printer, this is the rule to start with:
troubleshoot_printer 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 troubleshoot_printer call is checked against it from then on.
Questions about troubleshoot_printer
troubleshoot_printer 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 troubleshoot_printer: 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.
troubleshoot_printer 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 troubleshoot_printer 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 troubleshoot_printer. 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.
troubleshoot_printer 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