DescribeVirtualAccounts
[account] 列表虚拟组的账户，私有化调用path为：/capi/Assets/AccountVirtualGroup/DescribeVirtualAccounts，从7.x版本开始支持
This record as markdown: /tools/ioacloud-ioacloud-mcp/describevirtualaccounts.md
What DescribeVirtualAccounts does on Ioacloud
AI agents call DescribeVirtualAccounts to retrieve information from Ioacloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
Condition | object | — | 滤条件、分页参数 UserName - String - 是否必填：否 - 操作符: eq,like - 排序支持：否- 按用户名称过滤。 UserId - String - 是否必填：否 - 操作符: eq,like - 排序支持：否- 按用户账号过滤。 Phone - String - 是否必填：否 - 操作符: |
VirtualGroupId | number | Yes | 账户虚拟组Id(只支持32位) |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配 |
Parameters from the server's own tool schema.
Why DescribeVirtualAccounts is rated Low
Even though DescribeVirtualAccounts only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (27 properties)
Attacks that exploit this kind of access
The rule that runs DescribeVirtualAccounts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ioacloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For DescribeVirtualAccounts, this is the rule to start with:
DescribeVirtualAccounts 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 Ioacloud, apply this rule, and every DescribeVirtualAccounts call is checked against it from then on.
Questions about DescribeVirtualAccounts
[account] 列表虚拟组的账户，私有化调用path为：/capi/Assets/AccountVirtualGroup/DescribeVirtualAccounts，从7.x版本开始支持. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeVirtualAccounts accepts 3 parameters: Condition, VirtualGroupId, DomainInstanceId. Required: VirtualGroupId. The full parameter table on this page comes from the server's own tool schema.
Register the Ioacloud MCP server in PolicyLayer and add a rule for DescribeVirtualAccounts: 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 Ioacloud. Nothing to install.
DescribeVirtualAccounts 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 DescribeVirtualAccounts 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 DescribeVirtualAccounts. 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.
DescribeVirtualAccounts is provided by the Ioacloud MCP server (@ioacloud/ioacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ioacloud, and thousands of servers like it.
This server
Across the catalogue