runner_auth_setup
Install a selected runner CLI on the local or an owned endpoint and report readiness. This tool is install-only: it does not start OAuth, accept API keys, copy credentials, or modify the runner's MCP configuration. Sign in with the native CLI inside an encrypted PTY.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runner-auth-setup.md
What runner_auth_setup does on Yaver
AI agents invoke runner_auth_setup 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 owned endpoint ID |
install_if_missing | boolean | — | Default true. |
Parameters from the server's own tool schema.
Why runner_auth_setup is rated High
Installs software on local or remote endpoints, triggering external system changes.
From the tool's definition Install a selected runner CLI on the local or an owned endpoint
Attacks that exploit this kind of access
The rule that runs runner_auth_setup 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_setup, this is the rule to start with:
runner_auth_setup 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_setup call is checked against it from then on.
Questions about runner_auth_setup
Install a selected runner CLI on the local or an owned endpoint and report readiness. This tool is install-only: it does not start OAuth, accept API keys, copy credentials, or modify the runner's MCP configuration. Sign in with the native CLI inside an encrypted PTY. 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_setup accepts 3 parameters: runner, device_id, install_if_missing. 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 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_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.
More on Yaver, and thousands of servers like it.
Across the catalogue