primary_auth

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 20 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/primary-auth.md

WHAT IT DOES

What primary_auth does on Yaver

AI agents invoke primary_auth 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	—	Empty (default) for Yaver-level reauth; claude/claude-code or codex to start that runner's login flow on the primary device.
`confirm`	boolean	—	Explicitly replace/re-auth an existing runner credential. Default false; use only after the user requested it.

Parameters from the server's own tool schema.

RISK

Why primary_auth is rated High

Triggers authentication flows on remote devices, enabling session establishment with external services.

From the tool's definition kicks off runner's browser/device-code login flow, refreshes session token

Attacks that exploit this kind of access

RECOMMENDED RULE

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

primary_auth Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "primary_auth": {
      "limits": [
        {
          "counter": "primary_auth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about primary_auth

What does the primary_auth tool do? +

Re-auth on the user's primary remote device. With runner empty (default) this refreshes the Yaver session token via the existing /auth/recover flow (same as yaver primary auth). With runner=claude or codex, it kicks off the runner's browser/device-code login flow on the primary box (same as yaver primary auth claude / yaver primary auth codex); the response carries the URL/code the user opens to finish. Resolves the primary deviceId automatically — no need to look it up first. 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 primary_auth accept? +

primary_auth accepts 2 parameters: runner, confirm. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on primary_auth? +

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

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

Can I rate-limit primary_auth? +

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

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

primary_auth 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 678 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →