runner_auth_set

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 71 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-set.md

WHAT IT DOES

What runner_auth_set does on Yaver

AI agents use runner_auth_set 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
`glm_api_key`	string	—	OpenCode/GLM provider credential.
`zai_api_key`	string	—	OpenCode/GLM provider credential.
`openai_api_key`	string	—	OpenCode provider credential.
`anthropic_api_key`	string	—	OpenCode provider credential.

Parameters from the server's own tool schema.

RISK

Why runner_auth_set is rated Medium

This tool creates or modifies authentication and provider configuration data. While described as 'Legacy', it still performs credential/auth storage operations which, if misused by an agent (e.g., setting malicious provider credentials, writing to unintended peer devices), could compromise security and enable unauthorized access. The ability to write to 'another owned Yaver machine' adds lateral impact potential.

From the tool's definition The tool description states it writes authentication configuration to 'vault-backed provider auth' for OpenCode/GLM provider configuration, and explicitly mentions writing device_id 'to another owned Yaver machine'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs runner_auth_set 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_set, this is the rule to start with:

runner_auth_set Rate-limited

runner_auth_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runner_auth_set": {
      "limits": [
        {
          "counter": "runner_auth_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every runner_auth_set call is checked against it from then on.

FAQ

Questions about runner_auth_set

What does the runner_auth_set tool do? +

Legacy vault-backed provider auth for OpenCode/GLM provider configuration only. Claude Code and Codex use subscription OAuth through runner_auth_browser_start or runner_auth_credentials_import. Optional device_id writes to another owned Yaver machine. 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.

What parameters does runner_auth_set accept? +

runner_auth_set accepts 7 parameters: notes, runner, device_id, glm_api_key, zai_api_key, openai_api_key, anthropic_api_key. 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_set? +

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

runner_auth_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit runner_auth_set? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →