browser_interactive_stop

Stop an interactive co-browse session. The on-disk profile (cookies/auth) persists so later automation can reuse it.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-interactive-stop.md

WHAT IT DOES

What browser_interactive_stop does on Yaver

AI agents invoke browser_interactive_stop to trigger actions in Yaver. 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.

Parameter	Type	Required	Description
`session_id`	string	Yes	Interactive session ID

Parameters from the server's own tool schema.

RISK

Why browser_interactive_stop is rated High

This tool triggers an external operation (stopping a browser session) whose effects depend on which session is being terminated. While not destructive (the session state persists), it executes an action that manipulates browser automation state and authentication. The presence of cookie/auth persistence adds complexity but does not elevate it to Destructive since the profile data itself is preserved.

From the tool's definition Tool stops an 'interactive co-browse session' and manages persistent on-disk profiles with cookies and authentication data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_interactive_stop safely

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

browser_interactive_stop Rate-limited

browser_interactive_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": {
    "browser_interactive_stop": {
      "limits": [
        {
          "counter": "browser_interactive_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 Yaver, apply this rule, and every browser_interactive_stop call is checked against it from then on.

FAQ

Questions about browser_interactive_stop

What does the browser_interactive_stop tool do? +

Stop an interactive co-browse session. The on-disk profile (cookies/auth) persists so later automation can reuse it. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does browser_interactive_stop accept? +

browser_interactive_stop accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_interactive_stop? +

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

What risk level is browser_interactive_stop? +

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

Can I rate-limit browser_interactive_stop? +

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

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

browser_interactive_stop is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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