stop_screen_recording · AutoBot MCP: Risk & Policy

WHAT IT DOES

What stop_screen_recording does on AutoBot MCP

AI agents invoke stop_screen_recording 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_screen_recording needs a policy

This tool executes a command on a remote device to halt an ongoing process (screen recording). While not destructive (reversible—recording can be started again) or financial, it represents execution of a remote action whose effects depend on the device's current state. The low severity reflects that stopping a screen recording has minimal blast radius and no persistent side effects.

From the tool's definition Tool performs an action on a remote Android device (stopping screen recording) via the AutoBot API. The description states it 'Stop screen recording,' indicating it triggers an operation on the device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_screen_recording Rate-limited

stop_screen_recording 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_screen_recording": {
      "limits": [
        {
          "counter": "stop_screen_recording_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_screen_recording

What does the stop_screen_recording tool do? +

Stop screen recording. 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_screen_recording? +

Register the AutoBot MCP server in PolicyLayer and add a rule for stop_screen_recording: 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_screen_recording? +

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

Can I rate-limit stop_screen_recording? +

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

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

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