k1_emergency_stop · Execution Market MCP: Risk & Policy

WHAT IT DOES

What k1_emergency_stop does on Execution Market

AI agents invoke k1_emergency_stop to trigger actions in Execution Market. 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 IT NEEDS A POLICY

Why k1_emergency_stop needs a policy

This tool executes a command that triggers real-world mechanical/physical operations (actuators) with immediate and potentially irreversible consequences. While not inherently destructive in data terms, it performs an Execute action by running an external control operation.

From the tool's definition 'Halt every actuator immediately' describes triggering an external operation (emergency stop) whose effects depend on system state and argument interpretation. The word 'Halt' indicates immediate execution of a control command affecting real-world actuators.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

k1_emergency_stop Rate-limited

k1_emergency_stop 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": {
    "k1_emergency_stop": {
      "limits": [
        {
          "counter": "k1_emergency_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Execution Market, so you can run agents against it safely.

FAQ

Questions about k1_emergency_stop

What does the k1_emergency_stop tool do? +

Halt every actuator immediately. It is categorised as a Execute tool in the Execution Market MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on k1_emergency_stop? +

Register the Execution Market MCP server in PolicyLayer and add a rule for k1_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 Execution Market. Nothing to install.

What risk level is k1_emergency_stop? +

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

Can I rate-limit k1_emergency_stop? +

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

Set action: deny in the PolicyLayer policy for k1_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 k1_emergency_stop? +

k1_emergency_stop is provided by the Execution Market MCP server (https://mcp.execution.market/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.