emergency_trip_input

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-trip-input.md

WHAT IT DOES

What emergency_trip_input does on Kiln

AI agents invoke emergency_trip_input 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.

RISK

Why emergency_trip_input is rated High

The name 'emergency_trip_input' strongly suggests triggering an emergency stop or safety trip mechanism on a 3D printer. On industrial/printer control systems, an 'emergency trip' is a safety shutoff that immediately halts operations.

From the tool's definition Tool name 'emergency_trip_input' on a 3D printer control server (OctoPrint, Moonraker, Bambu, Prusa, Elegoo)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs emergency_trip_input 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 emergency_trip_input, this is the rule to start with:

emergency_trip_input Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "emergency_trip_input": {
      "limits": [
        {
          "counter": "emergency_trip_input_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every emergency_trip_input call is checked against it from then on.

FAQ

Questions about emergency_trip_input

What does the emergency_trip_input tool do? +

emergency_trip_input 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_trip_input? +

Register the Kiln MCP server in PolicyLayer and add a rule for emergency_trip_input: 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_trip_input? +

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

Can I rate-limit emergency_trip_input? +

Yes. Add a rate_limit block to the emergency_trip_input 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_trip_input completely? +

Set action: deny in the PolicyLayer policy for emergency_trip_input. 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_trip_input? +

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

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 402 Kiln tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →