runner_auth_browser_status

Read the live state of a previously-started runner browser-auth session on the local or a remote machine.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What runner_auth_browser_status does on Yaver

AI agents call runner_auth_browser_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
`device_id`	string	—	Optional remote device ID
`session_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why runner_auth_browser_status is rated Low

This is a read-only operation that queries the status of an existing authentication session. It retrieves information about a previously-started runner browser-auth session without modifying, executing, or destroying anything.

From the tool's definition The tool description explicitly states 'Read the live state' of a browser-auth session, with no ability to modify or alter that state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runner_auth_browser_status Allowed

runner_auth_browser_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": {
    "runner_auth_browser_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 runner_auth_browser_status call is checked against it from then on.

FAQ

Questions about runner_auth_browser_status

What does the runner_auth_browser_status tool do? +

Read the live state of a previously-started runner browser-auth session on the local or a remote machine. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does runner_auth_browser_status accept? +

runner_auth_browser_status accepts 2 parameters: device_id, 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 runner_auth_browser_status? +

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

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

Can I rate-limit runner_auth_browser_status? +

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

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

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