yaver_auth_link_start · Yaver MCP: Risk & Policy

WHAT IT DOES

What yaver_auth_link_start does on Yaver

AI agents invoke yaver_auth_link_start 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.

PARAMETERS

Parameter	Type	Required	Description
`provider`	string	Yes	Provider to link: apple \| github \| gitlab \| google \| microsoft

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why yaver_auth_link_start needs a policy

yaver_auth_link_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

yaver_auth_link_start Rate-limited

yaver_auth_link_start 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": {
    "yaver_auth_link_start": {
      "limits": [
        {
          "counter": "yaver_auth_link_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about yaver_auth_link_start

What does the yaver_auth_link_start tool do? +

Connect an ADDITIONAL OAuth provider to the currently signed-in account — e.g., user signed up with Apple but wants to also sign in with GitHub, GitLab, Google, or Microsoft. Returns {url, qr_ascii, link_token, expires_at_ms}. Render the URL + QR; the user opens it, signs in with that provider, and Yaver binds the provider to the existing account. Call yaver_auth_link_wait afterwards to confirm. 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 yaver_auth_link_start accept? +

yaver_auth_link_start accepts 1 parameter: provider. Required: provider. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on yaver_auth_link_start? +

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

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

Can I rate-limit yaver_auth_link_start? +

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

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

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