screencast_stop

Stops the active screencast recording on the selected page.

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/screencast-stop.md

WHAT IT DOES

What screencast_stop does on Chrome Devtools

AI agents invoke screencast_stop to trigger actions in Chrome Devtools. 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.

RISK

Why screencast_stop is rated High

screencast_stop executes a command that directly controls browser behavior and modifies the state of an active recording session. While not destructive (recording can be restarted), it is an Execute action because it runs a triggered operation on an external system (Chrome browser).

From the tool's definition The tool performs an action (stops a screencast recording) on a live browser session—this is an operation that triggers an external effect on the browser state, fitting the Execute category as it 'triggers external operations whose effects depend on arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs screencast_stop safely

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

screencast_stop Rate-limited

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every screencast_stop call is checked against it from then on.

FAQ

Questions about screencast_stop

What does the screencast_stop tool do? +

Stops the active screencast recording on the selected page. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screencast_stop? +

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

What risk level is screencast_stop? +

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

Can I rate-limit screencast_stop? +

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

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

screencast_stop is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →