DescribeLicenseUsageTimeHistogram
[team-lead] 获取License授权消耗趋势分布，私有化调用path为：capi/Report/DescribeLicenseUsageTimeHistogram
This record as markdown: /tools/ioacloud-ioacloud-mcp/describelicenseusagetimehistogram.md
What DescribeLicenseUsageTimeHistogram does on Ioacloud
AI agents call DescribeLicenseUsageTimeHistogram 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 |
|---|---|---|---|
OsType | string | — | 操作系统类型 -1:全部 0:win 1:linux 2:mac 4:android 5:ios |
EndTime | number | Yes | 结束时间 毫秒级时间戳 |
Filters | array | — | 过滤条件 |
StartTime | number | Yes | 开始时间 毫秒级时间戳 |
ModuleType | string | — | 模块类型 0:全部 1:无边界接入 2:终端安全 3:终端管控 4:安全准入 5:win7遁甲 6:水印保护 7:企业版软件管家 8:终端检查与响应(EDR) 9:远程桌面 |
Parameters from the server's own tool schema.
Why DescribeLicenseUsageTimeHistogram is rated Low
Even though DescribeLicenseUsageTimeHistogram 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.
Attacks that exploit this kind of access
The rule that runs DescribeLicenseUsageTimeHistogram 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 DescribeLicenseUsageTimeHistogram, this is the rule to start with:
DescribeLicenseUsageTimeHistogram 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 DescribeLicenseUsageTimeHistogram call is checked against it from then on.
Questions about DescribeLicenseUsageTimeHistogram
[team-lead] 获取License授权消耗趋势分布，私有化调用path为：capi/Report/DescribeLicenseUsageTimeHistogram. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeLicenseUsageTimeHistogram accepts 5 parameters: OsType, EndTime, Filters, StartTime, ModuleType. Required: EndTime, StartTime. 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 DescribeLicenseUsageTimeHistogram: 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.
DescribeLicenseUsageTimeHistogram 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 DescribeLicenseUsageTimeHistogram 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 DescribeLicenseUsageTimeHistogram. 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.
DescribeLicenseUsageTimeHistogram 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