yaver_auth_link_wait
Poll the account's linked identities until the requested provider appears (or timeout). Preferred over manual polling after yaver_auth_link_start. Default timeout 120s.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-link-wait.md
What yaver_auth_link_wait does on Yaver
AI agents call yaver_auth_link_wait to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
provider | string | Yes | The provider passed to yaver_auth_link_start |
timeout_seconds | integer | — | |
poll_interval_seconds | integer | — |
Parameters from the server's own tool schema.
Why yaver_auth_link_wait is rated Low
This tool only reads/queries the state of linked identities by polling until a condition is met or a timeout occurs. It does not create, modify, or delete any data — it is purely observational, waiting for an externally triggered change. Severity is low as misuse would at most waste time or cause a timeout.
From the tool's definition Poll the account's linked identities until the requested provider appears (or timeout)
Attacks that exploit this kind of access
The rule that runs yaver_auth_link_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 yaver_auth_link_wait, this is the rule to start with:
yaver_auth_link_wait is read-only, so it stays allowed. 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_auth_link_wait call is checked against it from then on.
Questions about yaver_auth_link_wait
Poll the account's linked identities until the requested provider appears (or timeout). Preferred over manual polling after yaver_auth_link_start. Default timeout 120s. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
yaver_auth_link_wait accepts 3 parameters: provider, timeout_seconds, poll_interval_seconds. Required: provider. 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_auth_link_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.
yaver_auth_link_wait is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the yaver_auth_link_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 yaver_auth_link_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.
yaver_auth_link_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.
This server
Across the catalogue