runner_auth_browser_cancel

Cancel a running runner browser-auth session on the local or a remote machine.

Server Yaver yaver-cli
Category Destructive
Risk class Critical
Parameters 21 required

What runner_auth_browser_cancel does on Yaver

AI agents call runner_auth_browser_cancel to permanently remove resources in Yaver — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
device_id string Optional remote device ID
session_id string Yes

Parameters from the server's own tool schema.

Why runner_auth_browser_cancel needs a policy

An AI agent that decides to call runner_auth_browser_cancel doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Yaver is gone — there is no undo for destructive operations.

Questions about runner_auth_browser_cancel

What does the runner_auth_browser_cancel tool do? +

Cancel a running runner browser-auth session on the local or a remote machine. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does runner_auth_browser_cancel accept? +

runner_auth_browser_cancel 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_cancel? +

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

runner_auth_browser_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit runner_auth_browser_cancel? +

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

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

runner_auth_browser_cancel 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.