stop_all_scripts · AutoBot MCP: Risk & Policy

WHAT IT DOES

What stop_all_scripts does on AutoBot MCP

AI agents invoke stop_all_scripts to trigger actions in AutoBot MCP. 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_all_scripts needs a policy

Stopping running scripts is an Execute action because it triggers a control operation over external processes and code execution on the device. While not destructive (scripts can be restarted), it forcibly terminates execution, which is a form of process control.

From the tool's definition Tool description: 'Stop all running AutoX.js scripts'. This terminates external script execution processes on the Android device, which is a control operation that affects running code/automation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_all_scripts Rate-limited

stop_all_scripts 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_all_scripts": {
      "limits": [
        {
          "counter": "stop_all_scripts_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 AutoBot MCP, so you can run agents against it safely.

FAQ

Questions about stop_all_scripts

What does the stop_all_scripts tool do? +

Stop all running AutoX.js scripts. It is categorised as a Execute tool in the AutoBot MCP 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_all_scripts? +

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

What risk level is stop_all_scripts? +

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

Can I rate-limit stop_all_scripts? +

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

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

stop_all_scripts is provided by the AutoBot MCP server (yz0903/autobot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

stop_all_scripts is one line of AutoBot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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