New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

account_list

List all cloud providers and their connection state.

SERVERYaver SOURCEyaver-cli
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about account_list

What does the account_list tool do? +

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.

How do I enforce a policy on account_list? +

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.

What risk level is account_list? +

account_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit account_list? +

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.

How do I block account_list completely? +

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.

What MCP server provides account_list? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.