获取 CLS 告警执行详情日志。查询指定时间范围内的告警策略执行详情，包括执行时间、结果、触发的日志内容等。 查询语法说明： - * : 查询所有告警策略的执行详情 - AlarmId:"alarm-xxx" : 查询指定告警策略的执行详情 - AlarmName:"告警名称" : 按告警名称查询 - 组合查询：AlarmId:"alarm-xxx" AND Status:"success" 分页说明：首次不传 Context；若返回 ListOver 为 false，用返回的 Context 获取后续数据。 返回信息包含：Results 列表（每条含 AlarmId、AlarmN...
Accepts freeform code/query input (Query)
Part of the Cls MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GetAlarmLog 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 GetAlarmLog 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:
GetAlarmLog:
rules:
- action: allowSee the full Cls policy for all 19 tools.
Agents calling read-class tools like GetAlarmLog 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 告警执行详情日志。查询指定时间范围内的告警策略执行详情，包括执行时间、结果、触发的日志内容等。 查询语法说明： - * : 查询所有告警策略的执行详情 - AlarmId:"alarm-xxx" : 查询指定告警策略的执行详情 - AlarmName:"告警名称" : 按告警名称查询 - 组合查询：AlarmId:"alarm-xxx" AND Status:"success" 分页说明：首次不传 Context；若返回 ListOver 为 false，用返回的 Context 获取后续数据。 返回信息包含：Results 列表（每条含 AlarmId、AlarmName、TopicId、TopicName、Trigger、TriggerCount、AlarmLevel、Status、CreateTime、Duration、NotifyStatus、Content）、Context（分页标识）、ListOver（是否查询完毕）。. 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 GetAlarmLog. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cls MCP server.
GetAlarmLog 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 GetAlarmLog 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 GetAlarmLog. 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.
GetAlarmLog 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