runner_auth_browser_status

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

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 21 required

What runner_auth_browser_status does on Yaver

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

ParameterTypeRequiredDescription
device_id string Optional remote device ID
session_id string Yes

Parameters from the server's own tool schema.

Why runner_auth_browser_status needs a policy

Even though runner_auth_browser_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.