This record as markdown: /tools/io-github-kivanccakmak-yaver/account-disconnect.md
What account_disconnect does on Yaver
AI agents use account_disconnect 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 |
Parameters from the server's own tool schema.
Why account_disconnect is rated Medium
This tool modifies security-critical data (stored credentials) irreversibly from the user's perspective, breaking authentication to external providers. While technically a deletion, it's classified as Write rather than Destructive because: (1) the credentials themselves are typically regenerated or re-entered rather than permanently destroyed at source, (2) the impact is localized to the client's stored state, and…
From the tool's definition Tool removes stored credentials for a provider. The description explicitly states 'Remove stored credentials', which is a destructive modification of authentication state.
Attacks that exploit this kind of access
The rule that runs account_disconnect 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 account_disconnect, this is the rule to start with:
account_disconnect 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 account_disconnect call is checked against it from then on.
Questions about account_disconnect
Remove stored credentials for a provider. 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.
account_disconnect accepts 1 parameter: provider. 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 account_disconnect: 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.
account_disconnect 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 account_disconnect 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 account_disconnect. 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.
account_disconnect 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