account_connect
Store credentials for a cloud provider (encrypted at rest).
This record as markdown: /tools/io-github-kivanccakmak-yaver/account-connect.md
What account_connect does on Yaver
AI agents use account_connect 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 |
|---|---|---|---|
label | string | — | |
fields | string | Yes | JSON: {"token":"..."} or {"accessKey":"...","secretKey":"..."} |
provider | string | Yes |
Parameters from the server's own tool schema.
Why account_connect is rated Medium
The tool creates or modifies stored authentication credentials, which is a reversible write operation. While credential storage is sensitive, the tool itself does not execute external operations, delete data, or move money. The encryption at rest mitigates some risk but does not change the category.
From the tool's definition Tool stores credentials for a cloud provider (encrypted at rest) — this is a create/modify operation that persistently records sensitive data.
Attacks that exploit this kind of access
The rule that runs account_connect 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_connect, this is the rule to start with:
account_connect 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_connect call is checked against it from then on.
Questions about account_connect
Store credentials for a cloud provider (encrypted at rest). 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_connect accepts 3 parameters: label, fields, provider. Required: fields, 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_connect: 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_connect 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_connect 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_connect. 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_connect 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