DescribeEventLogContent
[log] 查询EDR事件日志内容详情，需要传入ID，私有化调用path为：/capi/EDR/DescribeEventLogContent 前置：DescribeEvent 拿 EventId。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describeeventlogcontent.md
What DescribeEventLogContent does on Ioacloud
AI agents call DescribeEventLogContent 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 |
|---|---|---|---|
EventId | number | — | 事件ID |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配 |
LogContentSource | string | — | 日志内容来源(Event:告警事件(默认),GraphNode:证据节点) |
Parameters from the server's own tool schema.
Why DescribeEventLogContent is rated Low
Even though DescribeEventLogContent 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 DescribeEventLogContent 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 DescribeEventLogContent, this is the rule to start with:
DescribeEventLogContent 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 DescribeEventLogContent call is checked against it from then on.
Questions about DescribeEventLogContent
[log] 查询EDR事件日志内容详情，需要传入ID，私有化调用path为：/capi/EDR/DescribeEventLogContent 前置：DescribeEvent 拿 EventId。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeEventLogContent accepts 3 parameters: EventId, DomainInstanceId, LogContentSource. 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 DescribeEventLogContent: 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.
DescribeEventLogContent 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 DescribeEventLogContent 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 DescribeEventLogContent. 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.
DescribeEventLogContent 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