yaver_auth_merge_wait · Yaver MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

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 IT NEEDS A POLICY

Why yaver_auth_merge_wait needs a policy

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

Recommended rule Ready

Verdict

yaver_auth_merge_wait Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_auth_merge_wait": {
      "limits": [
        {
          "counter": "yaver_auth_merge_wait_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 yaver_auth_merge_wait

What does the yaver_auth_merge_wait tool do? +

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.

What parameters does yaver_auth_merge_wait accept? +

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.

How do I enforce a policy on yaver_auth_merge_wait? +

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.

What risk level is yaver_auth_merge_wait? +

yaver_auth_merge_wait is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit yaver_auth_merge_wait? +

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.

How do I block yaver_auth_merge_wait completely? +

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.

What MCP server provides yaver_auth_merge_wait? +

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.