yaver_auth_merge_start
Start a MANUAL account-merge: someone accidentally created two Yaver accounts and wants to fold one into the current one. Returns {merge_token, approval_url, qr_ascii, expires_at_ms, target_email}. The user opens the URL on a browser where the OTHER account is signed in, confirms, and the merge c...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-merge-start.md
What yaver_auth_merge_start does on Yaver
AI agents use yaver_auth_merge_start 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 |
|---|---|---|---|
totp_code | string | — | Optional 6-digit TOTP code for 2FA-protected accounts |
Parameters from the server's own tool schema.
Why yaver_auth_merge_start is rated Medium
This tool creates or modifies account state (merging two accounts) and can impact user identity and access. It is not destructive—the account data is folded into another account rather than deleted—and not financial in itself, though account control has financial implications.
From the tool's definition Tool description states it 'Start[s] a MANUAL account-merge' that 'fold[s] one [account] into the current one' and results in 'the merge completes'. This modifies account data by merging two accounts into one, a reversible but significant data modification.
Attacks that exploit this kind of access
The rule that runs yaver_auth_merge_start 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_start, this is the rule to start with:
yaver_auth_merge_start 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_start call is checked against it from then on.
Questions about yaver_auth_merge_start
Start a MANUAL account-merge: someone accidentally created two Yaver accounts and wants to fold one into the current one. Returns {merge_token, approval_url, qr_ascii, expires_at_ms, target_email}. The user opens the URL on a browser where the OTHER account is signed in, confirms, and the merge completes. Call yaver_auth_merge_wait to watch for completion. The currently signed-in account is the one that will be KEPT. If 2FA is enabled on the target account, pass totp_code. 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_start accepts 1 parameter: totp_code. 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_start: 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_start 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_start 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_start. 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_start 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