获取 CLS 告警历史记录。查询指定时间范围内的告警历史记录，包含告警触发、恢复等事件的详细信息，用于分析告警趋势和排查告警问题。 支持的过滤条件（Filters 参数）： - alarmId: 按告警策略 ID 过滤 - alarmName: 按告警策略名称过滤 - topicId: 按日志主题 ID 过滤 - status: 按告警状态过滤（0-未恢复，1-已恢复） 返回信息包含：TotalCount（总数）、Records 列表（每条记录含 RecordId、AlarmId、AlarmName、TopicId、TopicName、Region、Trigger、TriggerCo...
Part of the Cls MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call DescribeAlertRecordHistory to retrieve information from Cls without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though DescribeAlertRecordHistory only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
DescribeAlertRecordHistory:
rules:
- action: allowSee the full Cls policy for all 19 tools.
Agents calling read-class tools like DescribeAlertRecordHistory have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
获取 CLS 告警历史记录。查询指定时间范围内的告警历史记录，包含告警触发、恢复等事件的详细信息，用于分析告警趋势和排查告警问题。 支持的过滤条件（Filters 参数）： - alarmId: 按告警策略 ID 过滤 - alarmName: 按告警策略名称过滤 - topicId: 按日志主题 ID 过滤 - status: 按告警状态过滤（0-未恢复，1-已恢复） 返回信息包含：TotalCount（总数）、Records 列表（每条记录含 RecordId、AlarmId、AlarmName、TopicId、TopicName、Region、Trigger、TriggerCount、AlarmLevel、Status、CreateTime、Duration、NotifyStatus）。. It is categorised as a Read tool in the Cls MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for DescribeAlertRecordHistory. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cls MCP server.
DescribeAlertRecordHistory 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 DescribeAlertRecordHistory rule in your Intercept 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 Intercept policy for DescribeAlertRecordHistory. 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.
DescribeAlertRecordHistory is provided by the Cls MCP server (cls-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept