yaver_lazy_setup
One-shot install + auth + mobile-app handoff for a non-developer user being walked through setup by an AI agent. Call this FIRST instead of wiring up auth_status/start/wait manually. Returns a structured plan: whether yaver-cli is installed, whether the user is signed in, a sign-in URL (if needed...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-lazy-setup.md
What yaver_lazy_setup does on Yaver
AI agents invoke yaver_lazy_setup 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 |
|---|---|---|---|
wait_seconds | integer | — | If >0, block up to this many seconds (max 180) waiting for sign-in to complete in-call. Default 0 = return immediately. 120 is a reasonable value for agents tha |
Parameters from the server's own tool schema.
Why yaver_lazy_setup is rated High
This tool orchestrates installation of CLI software, authentication flows, and mobile app handoff — it triggers external operations (install, auth, device pairing) whose effects depend on system state. It goes beyond merely reading or writing data; it executes a multi-step setup process including software installation and account authentication.
From the tool's definition One-shot install + auth + mobile-app handoff... whether yaver-cli is installed, whether the user is signed in, a sign-in URL... mobile app install links (TestFlight + Play)... single `next_action` string the AI can speak verbatim
Attacks that exploit this kind of access
The rule that runs yaver_lazy_setup 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_lazy_setup, this is the rule to start with:
yaver_lazy_setup 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_lazy_setup call is checked against it from then on.
Questions about yaver_lazy_setup
One-shot install + auth + mobile-app handoff for a non-developer user being walked through setup by an AI agent. Call this FIRST instead of wiring up auth_status/start/wait manually. Returns a structured plan: whether yaver-cli is installed, whether the user is signed in, a sign-in URL (if needed) the AI should surface to the human, mobile app install links (TestFlight + Play), and a single next_action string the AI can speak verbatim. Idempotent: safe to call repeatedly while the user finishes steps on their phone — on each call it picks up where the last one left off. The ideal orchestration loop for a coding agent: (1) call yaver_lazy_setup → show the returned url to the human; (2) wait a bit; (3) call yaver_lazy_setup again — if status is now "signed_in", you're done. 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_lazy_setup accepts 1 parameter: wait_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 yaver_lazy_setup: 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_lazy_setup 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_lazy_setup 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_lazy_setup. 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_lazy_setup 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