DescribeLicenseAuthAccounts
[team-lead] 获取License授权账号管理列表，未授权账号，已授权账号，支持分页，模糊搜索，私有化调用path为：/capi/License/DescribeLicenseAuthAccounts 前置：DescribeGlobalLicense / DescribeSourceLicense 拿 LicenseDomainId。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describelicenseauthaccounts.md
What DescribeLicenseAuthAccounts does on Ioacloud
AI agents call DescribeLicenseAuthAccounts 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 |
|---|---|---|---|
ShowFlag | number | — | 是否仅展示当前目录下用户 1： 递归显示 2：仅显示当前目录下用户 |
AuthState | number | — | 获取授权账号的状态，1：未授权，2：已授权，不传默认为1 |
Condition | object | — | 滤条件、分页参数UserName - String - 是否必填：否 - 操作符: eq,like - 排序支持：否- 按账号UserName过滤。UserId - string - 是否必填：否 - 操作符: eq,like - 排序支持：否 - 按账号UserNd过滤。Phone - string - 是否必填：否 |
AccountGroupId | number | — | 获取账号的分组Id，不传默认获取全部 |
LicenseDomainId | number | — | License授权管理域id |
LicenseAuthModules | array | — | License授权模块 |
Parameters from the server's own tool schema.
Why DescribeLicenseAuthAccounts is rated Low
Even though DescribeLicenseAuthAccounts 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 (30 properties)
Attacks that exploit this kind of access
The rule that runs DescribeLicenseAuthAccounts 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 DescribeLicenseAuthAccounts, this is the rule to start with:
DescribeLicenseAuthAccounts 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 DescribeLicenseAuthAccounts call is checked against it from then on.
Questions about DescribeLicenseAuthAccounts
[team-lead] 获取License授权账号管理列表，未授权账号，已授权账号，支持分页，模糊搜索，私有化调用path为：/capi/License/DescribeLicenseAuthAccounts 前置：DescribeGlobalLicense / DescribeSourceLicense 拿 LicenseDomainId。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeLicenseAuthAccounts accepts 6 parameters: ShowFlag, AuthState, Condition, AccountGroupId, LicenseDomainId, LicenseAuthModules. 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 DescribeLicenseAuthAccounts: 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.
DescribeLicenseAuthAccounts 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 DescribeLicenseAuthAccounts 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 DescribeLicenseAuthAccounts. 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.
DescribeLicenseAuthAccounts 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