yaver_auth_wait
Block until the device code is authorized, expires, or the timeout fires. Preferred over yaver_auth_poll for coding agents that can accept a ~2-minute tool call. On authorized: saves token, starts daemon, registers MCP in editors. Default timeout 120s, poll interval 3s — both tunable.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-wait.md
What yaver_auth_wait does on Yaver
AI agents invoke yaver_auth_wait 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 | — | |
device_code | string | Yes | |
timeout_seconds | integer | — | Max seconds to block (default 120, max 300). |
poll_interval_seconds | integer | — | Seconds between polls (default 3). |
Parameters from the server's own tool schema.
Why yaver_auth_wait is rated High
This tool executes consequential operations: it waits for device authorization, persists authentication tokens, starts background processes (daemon), and registers the MCP server in editors. These are not mere data retrievals (Read) or reversible modifications (Write), but rather executable operations that establish system state and launch services.
From the tool's definition Blocks until device code is authorized, saves token, starts daemon, registers MCP in editors. The tool triggers external operations (daemon startup, MCP registration) and performs authentication state transitions whose side effects depend on device…
Attacks that exploit this kind of access
The rule that runs yaver_auth_wait 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_wait, this is the rule to start with:
yaver_auth_wait 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_wait call is checked against it from then on.
Questions about yaver_auth_wait
Block until the device code is authorized, expires, or the timeout fires. Preferred over yaver_auth_poll for coding agents that can accept a ~2-minute tool call. On authorized: saves token, starts daemon, registers MCP in editors. Default timeout 120s, poll interval 3s — both tunable. 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_wait accepts 4 parameters: convex_url, device_code, timeout_seconds, poll_interval_seconds. Required: device_code. 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_wait: 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_wait 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_wait 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_wait. 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_wait 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