yaver_auth_poll
Run one poll of the device-code authorization. Returns status = pending | authorized | expired. On authorized, the token is saved to ~/.yaver/config.json, the daemon is started in the background, and Yaver is auto-registered as an MCP server in every installed editor. Use this when you want full ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-poll.md
What yaver_auth_poll does on Yaver
AI agents invoke yaver_auth_poll 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 | Opaque device code returned by yaver_auth_start. |
Parameters from the server's own tool schema.
Why yaver_auth_poll is rated High
This tool does more than read data — upon successful authorization it writes credentials to disk, starts a background daemon process, and modifies configuration in every installed editor. These side effects (spawning processes, writing files, modifying editor configs) constitute execution of external operations with significant blast radius if misused by an AI agent.
From the tool's definition the token is saved to ~/.yaver/config.json, the daemon is started in the background, and Yaver is auto-registered as an MCP server in every installed editor
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs yaver_auth_poll 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_poll, this is the rule to start with:
yaver_auth_poll 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_poll call is checked against it from then on.
Questions about yaver_auth_poll
Run one poll of the device-code authorization. Returns status = pending | authorized | expired. On authorized, the token is saved to ~/.yaver/config.json, the daemon is started in the background, and Yaver is auto-registered as an MCP server in every installed editor. Use this when you want full control over polling cadence. 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_poll accepts 2 parameters: convex_url, device_code. 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_poll: 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_poll 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_poll 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_poll. 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_poll 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