AI agents invoke recovery_target_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 |
|---|---|---|---|
target_url | string | Yes | |
wait_token | string | Yes | |
recovery_id | string | Yes | |
relay_password | string | — | |
timeout_seconds | integer | — | Default 120, max 300. |
poll_interval_seconds | integer | — | Default 3. |
allow_public_direct_http | boolean | — |
Parameters from the server's own tool schema.
recovery_target_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
Poll a previously-started explicit-target recovery session until it completes, fails, or times out. Requires target_url plus the recovery_id/wait_token returned by recovery_target_start. 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.
recovery_target_wait accepts 7 parameters: target_url, wait_token, recovery_id, relay_password, timeout_seconds, poll_interval_seconds, allow_public_direct_http. Required: target_url, wait_token, recovery_id. 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 recovery_target_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.
recovery_target_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 recovery_target_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 recovery_target_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.
recovery_target_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.