High-level runner bootstrap for a local or remote Yaver machine: install the runner if missing, save auth into the Yaver vault, headless-login Codex with an API key when requested, and register Yaver as an MCP server inside the runner when supported.
AI agents use runner_auth_setup to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | |
runner | string | Yes | |
device_id | string | — | Optional remote device ID |
setup_mcp | boolean | — | Default true. Registers Yaver as an MCP server in the runner when supported. |
codex_login | boolean | — | Default true for Codex; ignored for other runners. |
glm_api_key | string | — | |
zai_api_key | string | — | |
openai_api_key | string | — | |
anthropic_api_key | string | — | |
allow_install_only | boolean | — | Return a soft success when the CLI is installed but auth is still pending. |
install_if_missing | boolean | — | Default true. |
anthropic_auth_token | string | — |
Parameters from the server's own tool schema.
An AI agent can call runner_auth_setup faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
High-level runner bootstrap for a local or remote Yaver machine: install the runner if missing, save auth into the Yaver vault, headless-login Codex with an API key when requested, and register Yaver as an MCP server inside the runner when supported. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
runner_auth_setup accepts 12 parameters: notes, runner, device_id, setup_mcp, codex_login, glm_api_key, zai_api_key, openai_api_key, anthropic_api_key, allow_install_only, install_if_missing, anthropic_auth_token. Required: runner. 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_setup: 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_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the runner_auth_setup 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_setup. 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_setup 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.