New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

emergency_stop

A execute tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/emergency-stop.md

What emergency_stop does on Kiln

AI agents invoke emergency_stop 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 emergency_stop is rated High

Emergency stop is an Execute action because it triggers an external operation (halting a 3D printer mid-operation) whose effects are immediate and depend on the printer's current state. Severity is critical because misuse could cause hardware damage, safety hazards (hot nozzles, bed), material waste, or unattended fire risk.

From the tool's definition Tool name is 'emergency_stop' in a 3D printer control system (OctoPrint, Moonraker, Bambu, Prusa, Elegoo). Despite empty description, the name unambiguously indicates triggering an emergency stop action on active printing equipment.

Questions about emergency_stop

What does the emergency_stop tool do? +

emergency_stop 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.

How do I enforce a policy on emergency_stop? +

Register the Kiln MCP server in PolicyLayer and add a rule for emergency_stop: 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.

What risk level is emergency_stop? +

emergency_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit emergency_stop? +

Yes. Add a rate_limit block to the emergency_stop 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.

How do I block emergency_stop completely? +

Set action: deny in the PolicyLayer policy for emergency_stop. 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.

What MCP server provides emergency_stop? +

emergency_stop 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kiln's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.