yaver_auth_unlink
Remove an OAuth provider from the currently signed-in account. Refuses if it is the ONLY sign-in method (would lock the user out). If the unlinked provider was the primary one, another linked provider is promoted automatically. If 2FA is enabled, pass totp_code.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-unlink.md
What yaver_auth_unlink does on Yaver
AI agents use yaver_auth_unlink 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 |
|---|---|---|---|
provider | string | Yes | apple | github | gitlab | google | microsoft | email |
totp_code | string | — | Optional 6-digit TOTP code for 2FA-protected accounts |
Parameters from the server's own tool schema.
Why yaver_auth_unlink is rated Medium
This tool removes (unlinks) an OAuth provider from an account, which is a reversible modification — the provider could be re-linked later. It is not fully destructive since it refuses to lock the user out (requires at least one remaining method) and auto-promotes another provider if needed. It modifies account authentication configuration, making Write the appropriate category.
From the tool's definition Remove an OAuth provider from the currently signed-in account
Attacks that exploit this kind of access
The rule that runs yaver_auth_unlink 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_unlink, this is the rule to start with:
yaver_auth_unlink 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_unlink call is checked against it from then on.
Questions about yaver_auth_unlink
Remove an OAuth provider from the currently signed-in account. Refuses if it is the ONLY sign-in method (would lock the user out). If the unlinked provider was the primary one, another linked provider is promoted automatically. If 2FA is enabled, 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_unlink accepts 2 parameters: provider, totp_code. 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_unlink: 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_unlink 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_unlink 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_unlink. 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_unlink 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