DescribeDLPAlarmHit
[dlp] DLP告警命中信息，私有化调用path为：capi/DlpOpenApi/DescribeDLPAlarmHit 前置：DescribeDLPAlarm 拿 AlarmId。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describedlpalarmhit.md
What DescribeDLPAlarmHit does on Ioacloud
AI agents call DescribeDLPAlarmHit 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 |
|---|---|---|---|
Source | number | — | 标识是终端还是企微告警：7780 终端审计日志， 7785 企微审计日志(只支持32位) |
Content | string | — | 匹配内容 |
HitType | string | — | 类型 category file |
PolicyId | number | — | 告警策略ID |
AlarmTime | string | — | 告警时间 |
AuditUUID | array | — | 匹配AuditUUID |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配。若企业未进行管理域的划分，可直接传入根域"1"，此时表示针对当前企业的全部设备和账号进行接口CRUD，具体CRUD的影响范围限制于相应接口的入参。 |
Parameters from the server's own tool schema.
Why DescribeDLPAlarmHit is rated Low
Even though DescribeDLPAlarmHit 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 signalsAccepts raw HTML/template content (Content)
Attacks that exploit this kind of access
The rule that runs DescribeDLPAlarmHit 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 DescribeDLPAlarmHit, this is the rule to start with:
DescribeDLPAlarmHit 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 DescribeDLPAlarmHit call is checked against it from then on.
Questions about DescribeDLPAlarmHit
[dlp] DLP告警命中信息，私有化调用path为：capi/DlpOpenApi/DescribeDLPAlarmHit 前置：DescribeDLPAlarm 拿 AlarmId。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeDLPAlarmHit accepts 7 parameters: Source, Content, HitType, PolicyId, AlarmTime, AuditUUID, 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 DescribeDLPAlarmHit: 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.
DescribeDLPAlarmHit 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 DescribeDLPAlarmHit 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 DescribeDLPAlarmHit. 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.
DescribeDLPAlarmHit 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