runner_auth_browser_start

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 21 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/runner-auth-browser-start.md

WHAT IT DOES

What runner_auth_browser_start does on Yaver

AI agents invoke runner_auth_browser_start 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
`runner`	string	Yes
`device_id`	string	—	Optional remote device ID

Parameters from the server's own tool schema.

RISK

Why runner_auth_browser_start is rated High

This tool executes an authentication flow that interacts with external services (Claude/ChatGPT OAuth providers) and modifies local/remote machine state (login credentials, session tokens). While ostensibly for legitimate user auth, an AI agent given control could initiate unwanted authentication flows, potentially on remote machines, or use this as a vector to establish persistent access.

From the tool's definition 'Start the interactive plan-OAuth browser/device-auth login flow' — initiates an external OAuth authentication process with side effects dependent on user interaction and network state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

runner_auth_browser_start Rate-limited

runner_auth_browser_start 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": {
    "runner_auth_browser_start": {
      "limits": [
        {
          "counter": "runner_auth_browser_start_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 runner_auth_browser_start call is checked against it from then on.

FAQ

Questions about runner_auth_browser_start

What does the runner_auth_browser_start tool do? +

Start the interactive plan-OAuth browser/device-auth login flow for Claude Code or Codex on the local or a remote Yaver machine. Uses the user's Claude Pro/Max or ChatGPT Plus/Pro account on their own device; no API key is requested. 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 runner_auth_browser_start accept? +

runner_auth_browser_start accepts 2 parameters: runner, device_id. Required: runner. 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_start? +

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

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

Can I rate-limit runner_auth_browser_start? +

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

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

runner_auth_browser_start 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 →team_manager_start_room on Team Manager MCP →start_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 →