browser_interactive_status

Get the current URL and title of an interactive co-browse session — poll this to detect when the human has finished logging in / solving the captcha.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What browser_interactive_status does on Yaver

AI agents call browser_interactive_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

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

Parameters from the server's own tool schema.

RISK

Why browser_interactive_status is rated Low

This tool queries the state of an interactive co-browse session to retrieve the current URL and title. It performs no writes, deletions, code execution, or financial operations. Even though it is used to monitor user actions (login/captcha completion), it is fundamentally a passive data retrieval mechanism.

From the tool's definition Tool description explicitly states 'Get the current URL and title' — a retrieval operation with no side effects. The verb 'Get' and the polling use case (detecting state changes without modifying them) confirm read-only behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_interactive_status 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_status, this is the rule to start with:

browser_interactive_status Allowed

browser_interactive_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_interactive_status": {}
  }
}

ALLOW ONLY 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_status call is checked against it from then on.

FAQ

Questions about browser_interactive_status

What does the browser_interactive_status tool do? +

Get the current URL and title of an interactive co-browse session — poll this to detect when the human has finished logging in / solving the captcha. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does browser_interactive_status accept? +

browser_interactive_status 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_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for browser_interactive_status: 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_status? +

browser_interactive_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_interactive_status? +

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

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

browser_interactive_status 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 →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server →browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →