stop · KentraBOT MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop does on KentraBOT MCP Server

AI agents invoke stop to trigger actions in KentraBOT MCP Server. 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 stop needs a policy

This tool executes a command that directly controls physical robot motors. While not destructive (the robot can be restarted), it is Execute-category because it runs an external operation whose real-world effects depend on context (stopping an active robot is different from stopping an idle one).

From the tool's definition Tool name is 'stop' with description 'Emergency stop. Halts both motors immediately.' This triggers an immediate external operation on physical hardware (a two-track robot's motors) whose effects are instantaneous and dependent on the robot's current…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop Rate-limited

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": {
    "stop": {
      "limits": [
        {
          "counter": "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 KentraBOT MCP Server, so you can run agents against it safely.

FAQ

Questions about stop

What does the stop tool do? +

Emergency stop. Halts both motors immediately. It is categorised as a Execute tool in the KentraBOT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop? +

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

What risk level is stop? +

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

Can I rate-limit stop? +

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

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

stop is provided by the KentraBOT MCP Server MCP server (kentra/kentrabot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.