runner_auth_browser_submit_callback
Deliver a localhost OAuth callback URL (http://localhost:<port>/callback?...) into a running runner browser-auth session on the local or a remote machine. Use when the user finished the sign-in in a browser on a DIFFERENT device than the runner: the browser lands on that device's localhost and th...
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-auth-browser-submit-callback.md
What runner_auth_browser_submit_callback does on Yaver
AI agents invoke runner_auth_browser_submit_callback 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 |
|---|---|---|---|
device_id | string | — | Optional remote device ID |
session_id | string | Yes | |
callback_url | string | Yes | Full localhost callback URL copied from the browser address bar. |
Parameters from the server's own tool schema.
Why runner_auth_browser_submit_callback is rated High
This tool injects an OAuth callback URL into an active authentication session, effectively completing an OAuth flow on behalf of a user. This is an Execute action because it triggers an external authentication operation whose effects depend on the submitted URL. Misuse could allow an attacker to hijack OAuth sessions or authenticate as another user, making severity high.
From the tool's definition Deliver a localhost OAuth callback URL into a running runner browser-auth session... this verb replays the pasted URL to the runner's waiting loopback listener
Risk signalsAccepts URL/endpoint input (callback_url)
Attacks that exploit this kind of access
The rule that runs runner_auth_browser_submit_callback 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_submit_callback, this is the rule to start with:
runner_auth_browser_submit_callback 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every runner_auth_browser_submit_callback call is checked against it from then on.
Questions about runner_auth_browser_submit_callback
Deliver a localhost OAuth callback URL (http://localhost:<port>/callback?...) into a running runner browser-auth session on the local or a remote machine. Use when the user finished the sign-in in a browser on a DIFFERENT device than the runner: the browser lands on that device's localhost and the runner CLI never sees the code — this verb replays the pasted URL to the runner's waiting loopback listener. The URL must match the session's observed callback port; validation is identical to the web/mobile Deliver-callback lane. 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.
runner_auth_browser_submit_callback accepts 3 parameters: device_id, session_id, callback_url. Required: session_id, callback_url. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for runner_auth_browser_submit_callback: 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.
runner_auth_browser_submit_callback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runner_auth_browser_submit_callback 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.
Set action: deny in the PolicyLayer policy for runner_auth_browser_submit_callback. 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.
runner_auth_browser_submit_callback 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.
More on Yaver, and thousands of servers like it.
Across the catalogue