device_reauth_wait
Wait for remote Yaver auth recovery to complete. Preferred usage is recovery_id + wait_token from device_reauth_start; device_id-only fallback still probes machine health for older callers.
This record as markdown: /tools/io-github-kivanccakmak-yaver/device-reauth-wait.md
What device_reauth_wait does on Yaver
AI agents invoke device_reauth_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 |
|---|---|---|---|
device_id | string | — | Owned device selector. Required for remote-session waits; optional only when waiting on a local session. |
wait_token | string | — | |
recovery_id | string | — | |
timeout_seconds | integer | — | Default 120, max 300. |
poll_interval_seconds | integer | — | Default 3. |
Parameters from the server's own tool schema.
Why device_reauth_wait is rated High
This tool executes an operation that waits for and completes a remote authentication recovery process. While the actual authentication state change happens server-side, the tool is triggering/monitoring that operation. It does not irreversibly delete data (Destructive), move money (Financial), or merely query state (Read) — it actively engages an external authentication workflow. This is Execute-category.
From the tool's definition 'Wait for remote Yaver auth recovery to complete' indicates the tool triggers an external operation (authentication recovery process) whose outcome depends on the provided arguments (recovery_id, wait_token, or device_id).
Attacks that exploit this kind of access
The rule that runs device_reauth_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 device_reauth_wait, this is the rule to start with:
device_reauth_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 device_reauth_wait call is checked against it from then on.
Questions about device_reauth_wait
Wait for remote Yaver auth recovery to complete. Preferred usage is recovery_id + wait_token from device_reauth_start; device_id-only fallback still probes machine health for older callers. 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.
device_reauth_wait accepts 5 parameters: device_id, wait_token, recovery_id, timeout_seconds, poll_interval_seconds. 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 device_reauth_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.
device_reauth_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 device_reauth_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 device_reauth_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.
device_reauth_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