This record as markdown: /tools/kiln/restart-server.md
What restart_server does on Kiln
AI agents invoke restart_server 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 restart_server is rated High
restart_server performs an irrevocable operational action (server restart) whose effects are substantial but not data-destructive or financial. It is Execute rather than Destructive because the restart itself is reversible (the server comes back up) and does not permanently delete data. High severity reflects the potential to disrupt active 3D print jobs and temporarily disable printer access.
From the tool's definition Tool name is 'restart_server'; description is empty. In the context of a 3D printer control server (OctoPrint, Moonraker, Bambu, Prusa, Elegoo), restarting the server triggers an external operation with significant effects: interruption of print jobs, loss of…
Attacks that exploit this kind of access
The rule that runs restart_server 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 restart_server, this is the rule to start with:
restart_server 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 restart_server call is checked against it from then on.
Questions about restart_server
restart_server 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 restart_server: 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.
restart_server 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 restart_server 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 restart_server. 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.
restart_server 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