This record as markdown: /tools/io-github-kivanccakmak-yaver/account-list.md
What account_list does on Yaver
AI agents call account_list to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why account_list is rated Low
This tool retrieves and displays account/connection status information. It performs no state changes, does not execute operations, and does not delete or move data. Listing accounts and their connection states is a read-only operation with minimal security impact unless the list itself is considered sensitive—but exposure would be informational rather than immediately exploitable.
From the tool's definition Tool name 'account_list' and description 'List all cloud providers and their connection state' indicate a query operation that retrieves information without modification or side effects.
Attacks that exploit this kind of access
The rule that runs account_list 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_list, this is the rule to start with:
account_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about account_list
List all cloud providers and their connection state. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for account_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the account_list 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_list. 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_list 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