device_reauth_start · Yaver MCP: Risk & Policy

WHAT IT DOES

What device_reauth_start does on Yaver

AI agents invoke device_reauth_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.

PARAMETERS

Parameter	Type	Required	Description
`mode`	string	—	auto (default), direct, pair, or device-code.
`device_id`	string	Yes	Owned Yaver device ID, unique prefix, or exact device name.
`bootstrap_secret`	string	—	Optional legacy bootstrap secret for secret-based recovery when host-token recovery is not enough.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why device_reauth_start needs a policy

device_reauth_start 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_start Rate-limited

device_reauth_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.

View as policy code

policy.json

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

What does the device_reauth_start tool do? +

Start Yaver re-auth on an owned remote machine through the existing /auth/recover path. auto picks the safest mode for the detected state: typically direct for auth-expired, pair for bootstrap. 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_start accept? +

device_reauth_start accepts 3 parameters: mode, device_id, bootstrap_secret. Required: device_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on device_reauth_start? +

Register the Yaver MCP server in PolicyLayer and add a rule for device_reauth_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.

What risk level is device_reauth_start? +

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

Can I rate-limit device_reauth_start? +

Yes. Add a rate_limit block to the device_reauth_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.

How do I block device_reauth_start completely? +

Set action: deny in the PolicyLayer policy for device_reauth_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.

What MCP server provides device_reauth_start? +

device_reauth_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.