stop_run

Stop (cancel) a run immediately. A stopped run cannot be resumed; the robot homes and drops

SERVERPypi:labmcp Alicat SOURCEpypi:labmcp-alicat

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lab-instrument-mcps/stop-run.md

WHAT IT DOES

What stop_run does on Pypi:labmcp Alicat

AI agents call stop_run to permanently remove resources in Pypi:labmcp Alicat, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why stop_run is rated Critical

Irreversibly cancels a lab run; robot homes and drops, cannot be resumed.

From the tool's definition Stop (cancel) a run immediately... cannot be resumed

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:labmcp Alicat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_run, this is the rule to start with:

stop_run Hidden

stop_run is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "stop_run"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about stop_run

What does the stop_run tool do? +

Stop (cancel) a run immediately. A stopped run cannot be resumed; the robot homes and drops. It is categorised as a Destructive tool in the Pypi:labmcp Alicat MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on stop_run? +

Register the Pypi:labmcp Alicat MCP server in PolicyLayer and add a rule for stop_run: 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 Pypi:labmcp Alicat. Nothing to install.

What risk level is stop_run? +

stop_run is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stop_run? +

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

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

stop_run is provided by the Pypi:labmcp Alicat MCP server (pypi:labmcp-alicat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pypi:labmcp Alicat, and thousands of servers like it.

This server

All 242 Pypi:labmcp Alicat tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →