yaver_auth_merge_wait
Poll a merge intent's status until it completes, is cancelled, or expires. Default timeout 180s.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-merge-wait.md
What yaver_auth_merge_wait does on Yaver
AI agents use yaver_auth_merge_wait to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
merge_token | string | Yes | Token returned by yaver_auth_merge_start |
timeout_seconds | integer | — | |
poll_interval_seconds | integer | — |
Parameters from the server's own tool schema.
Why yaver_auth_merge_wait is rated Medium
An AI agent can call yaver_auth_merge_wait faster than any human can review: one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs yaver_auth_merge_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_merge_wait, this is the rule to start with:
yaver_auth_merge_wait stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_auth_merge_wait call is checked against it from then on.
Questions about yaver_auth_merge_wait
Poll a merge intent's status until it completes, is cancelled, or expires. Default timeout 180s. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
yaver_auth_merge_wait accepts 3 parameters: merge_token, timeout_seconds, poll_interval_seconds. Required: merge_token. 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_merge_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_merge_wait is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the yaver_auth_merge_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_merge_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_merge_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