yaver_auth_start
Start a headless device-code sign-in for Yaver (Apple / GitHub / Google / Microsoft OAuth, passkey, or email-password if enabled on the deployment). Returns {url, user_code, device_code, qr_ascii, expires_at_ms}. Render the URL + QR to the user; they open it on their phone or laptop browser, sign...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-start.md
What yaver_auth_start does on Yaver
AI agents invoke yaver_auth_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
convex_url | string | — | Optional override for the Convex backend URL (defaults to the stored or hosted endpoint). |
Parameters from the server's own tool schema.
Why yaver_auth_start is rated High
This is Execute rather than Write because it triggers an external authentication flow and returns tokens/codes that enable subsequent operations, rather than directly creating/modifying persistent data. The tool itself performs the authentication initiation action ('Start...sign-in'), which is an operation with side effects.
From the tool's definition Tool initiates OAuth device-code sign-in flow and returns authentication credentials (device_code, user_code, url).
Attacks that exploit this kind of access
The rule that runs yaver_auth_start 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 yaver_auth_start, this is the rule to start with:
yaver_auth_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every yaver_auth_start call is checked against it from then on.
Questions about yaver_auth_start
Start a headless device-code sign-in for Yaver (Apple / GitHub / Google / Microsoft OAuth, passkey, or email-password if enabled on the deployment). Returns {url, user_code, device_code, qr_ascii, expires_at_ms}. Render the URL + QR to the user; they open it on their phone or laptop browser, sign in, and confirm the code. Then call yaver_auth_wait (or loop yaver_auth_poll) with the device_code to finish. Non-blocking — this tool does not wait for the user. 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.
yaver_auth_start accepts 1 parameter: convex_url. 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 yaver_auth_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.
yaver_auth_start 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 yaver_auth_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.
Set action: deny in the PolicyLayer policy for yaver_auth_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.
yaver_auth_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.
More on Yaver, and thousands of servers like it.
Across the catalogue