DescribeLogTimeHistogram
[log] 目前支持:上网拦截日志(上网拦截概览); 风险分析日志(产生风险事件的用户数趋势)，私有化调用path为：capi/Report/DescribeLogTimeHistogram 前置：DescribeLogCondition 拿字段字典。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describelogtimehistogram.md
What DescribeLogTimeHistogram does on Ioacloud
AI agents call DescribeLogTimeHistogram 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 |
|---|---|---|---|
Field | string | Yes | 聚合查询的字段 |
LogId | string | Yes | 日志命令字 |
EndTime | number | Yes | 结束时间 |
Filters | array | — | 过滤条件 |
Interval | string | Yes | 周期时间间隔 |
StartTime | number | Yes | 起始时间 |
Department | number | — | 部门ID |
HistogramField | string | Yes | 按时间分桶的字段 |
Parameters from the server's own tool schema.
Why DescribeLogTimeHistogram is rated Low
Even though DescribeLogTimeHistogram 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 (12 properties)
Attacks that exploit this kind of access
The rule that runs DescribeLogTimeHistogram 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 DescribeLogTimeHistogram, this is the rule to start with:
DescribeLogTimeHistogram 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 DescribeLogTimeHistogram call is checked against it from then on.
Questions about DescribeLogTimeHistogram
[log] 目前支持:上网拦截日志(上网拦截概览); 风险分析日志(产生风险事件的用户数趋势)，私有化调用path为：capi/Report/DescribeLogTimeHistogram 前置：DescribeLogCondition 拿字段字典。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeLogTimeHistogram accepts 8 parameters: Field, LogId, EndTime, Filters, Interval, StartTime, Department, HistogramField. Required: Field, LogId, EndTime, Interval, StartTime, HistogramField. 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 DescribeLogTimeHistogram: 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.
DescribeLogTimeHistogram 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 DescribeLogTimeHistogram 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 DescribeLogTimeHistogram. 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.
DescribeLogTimeHistogram 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