通过告警详情 URL 获取 CLS 告警的详细信息。从告警通知中的 URL 提取并解析告警信息，支持短链接和长链接格式。 支持的 URL 格式： 1. 短链接：https://alarm.cls.tencentcs.com/WeNZ5sSP 2. 短链接：https://mc.tencent.com/xxx 3. 长链接：https://ap-guangzhou-monitor.cls.tencentcs.com/cls_no_login?action=GetAlertDetailPage#/alert?RecordId=xxx 返回 Markdown 格式的告警详细信息，包含： -...
Part of the Cls MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GetAlarmDetail 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 GetAlarmDetail 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:
GetAlarmDetail:
rules:
- action: allowSee the full Cls policy for all 19 tools.
Agents calling read-class tools like GetAlarmDetail 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.
通过告警详情 URL 获取 CLS 告警的详细信息。从告警通知中的 URL 提取并解析告警信息，支持短链接和长链接格式。 支持的 URL 格式： 1. 短链接：https://alarm.cls.tencentcs.com/WeNZ5sSP 2. 短链接：https://mc.tencent.com/xxx 3. 长链接：https://ap-guangzhou-monitor.cls.tencentcs.com/cls_no_login?action=GetAlertDetailPage#/alert?RecordId=xxx 返回 Markdown 格式的告警详细信息，包含： - 告警基本信息（名称、ID、地域） - 告警详细数据（监控对象、触发时间、持续时间、触发条件） - 触发语句（CQL 查询） - 多维分析结果（字段分布、查询结果表格） 应用场景：直接粘贴告警通知中的 URL 即可获取完整告警信息，用于快速排查和分析。. 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 GetAlarmDetail. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cls MCP server.
GetAlarmDetail 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 GetAlarmDetail 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 GetAlarmDetail. 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.
GetAlarmDetail 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