获取 CLS 告警屏蔽规则列表。查询指定通知渠道组下的告警屏蔽规则，屏蔽规则用于在特定时间段内屏蔽告警通知，避免维护期间产生大量告警噪音。 应用场景： 1. 查看某个通知渠道组下配置的所有屏蔽规则 2. 查询当前生效的屏蔽规则（按状态过滤） 3. 审计和管理告警屏蔽配置 支持的过滤条件（Filters 参数）： - shieldId: 按屏蔽规则 ID 过滤，如 [{Key: 'shieldId', Values: ['shield-xxx']}] - name: 按屏蔽规则名称过滤，如 [{Key: 'name', Values: ['维护屏蔽']}] - status: 按状态过滤（...
Part of the Cls server.
Free to start. No card required.
AI agents call DescribeAlarmShields 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 DescribeAlarmShields 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.
{
"version": "1",
"default": "deny",
"tools": {
"DescribeAlarmShields": {}
}
}See the full Cls policy for all 19 tools.
These attack patterns abuse exactly the kind of access DescribeAlarmShields gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
获取 CLS 告警屏蔽规则列表。查询指定通知渠道组下的告警屏蔽规则，屏蔽规则用于在特定时间段内屏蔽告警通知，避免维护期间产生大量告警噪音。 应用场景： 1. 查看某个通知渠道组下配置的所有屏蔽规则 2. 查询当前生效的屏蔽规则（按状态过滤） 3. 审计和管理告警屏蔽配置 支持的过滤条件（Filters 参数）： - shieldId: 按屏蔽规则 ID 过滤，如 [{Key: 'shieldId', Values: ['shield-xxx']}] - name: 按屏蔽规则名称过滤，如 [{Key: 'name', Values: ['维护屏蔽']}] - status: 按状态过滤（enabled=启用，disabled=禁用），如 [{Key: 'status', Values: ['enabled']}]. It is categorised as a Read tool in the Cls MCP Server, which means it retrieves data without modifying state.
Register the Cls MCP server in PolicyLayer and add a rule for DescribeAlarmShields: 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 Cls. Nothing to install.
DescribeAlarmShields 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 DescribeAlarmShields 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 DescribeAlarmShields. 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.
DescribeAlarmShields is provided by the Cls MCP server (cls-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Cls tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.