DescribeReportEventTimeCountByATTCK
[incident] EDR报表查询-值得关注ATTCK类型告警总数时间趋势-，私有化调用path为：/capi/EDR/DescribeReportEventTimeCountByATTCK
This record as markdown: /tools/ioacloud-ioacloud-mcp/describereporteventtimecountbyattck.md
What DescribeReportEventTimeCountByATTCK does on Ioacloud
AI agents call DescribeReportEventTimeCountByATTCK 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 |
|---|---|---|---|
TechKeys | array | — | Common:ATTCK目标Keys |
TimeUnit | string | — | 统计时间单位（hour.小时 day.天） |
EndTimestamp | number | — | 结束时间戳 |
StartTimestamp | number | — | 开始时间戳 |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配 |
Parameters from the server's own tool schema.
Why DescribeReportEventTimeCountByATTCK is rated Low
Even though DescribeReportEventTimeCountByATTCK 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 DescribeReportEventTimeCountByATTCK 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 DescribeReportEventTimeCountByATTCK, this is the rule to start with:
DescribeReportEventTimeCountByATTCK 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 DescribeReportEventTimeCountByATTCK call is checked against it from then on.
Questions about DescribeReportEventTimeCountByATTCK
[incident] EDR报表查询-值得关注ATTCK类型告警总数时间趋势-，私有化调用path为：/capi/EDR/DescribeReportEventTimeCountByATTCK. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeReportEventTimeCountByATTCK accepts 5 parameters: TechKeys, TimeUnit, EndTimestamp, StartTimestamp, DomainInstanceId. 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 DescribeReportEventTimeCountByATTCK: 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.
DescribeReportEventTimeCountByATTCK 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 DescribeReportEventTimeCountByATTCK 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 DescribeReportEventTimeCountByATTCK. 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.
DescribeReportEventTimeCountByATTCK 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