device_reauth_wait · Yaver MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

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 IT NEEDS A POLICY

Why device_reauth_wait needs a policy

device_reauth_wait 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

device_reauth_wait Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "device_reauth_wait": {
      "limits": [
        {
          "counter": "device_reauth_wait_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 device_reauth_wait

What does the device_reauth_wait tool do? +

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.

What parameters does device_reauth_wait accept? +

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.

How do I enforce a policy on device_reauth_wait? +

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.

What risk level is device_reauth_wait? +

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

Can I rate-limit device_reauth_wait? +

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.

How do I block device_reauth_wait completely? +

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.

What MCP server provides device_reauth_wait? +

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.