New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 31 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-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.

ParameterTypeRequiredDescription
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

Questions about runner_auth_setup

What does the runner_auth_setup tool do? +

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.

What parameters does runner_auth_setup accept? +

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.

How do I enforce a policy on runner_auth_setup? +

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.

What risk level is runner_auth_setup? +

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

Can I rate-limit runner_auth_setup? +

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.

How do I block runner_auth_setup completely? +

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.

What MCP server provides runner_auth_setup? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.