更新报警清除规则
AI agents use update_warning_clean to create or update resources in AIRIOT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIRIOT MCP Server environment.
This tool modifies alarm clearance rules within the IoT platform. While it creates side effects by changing alarm behavior, the operation is reversible (the rule can be updated again), distinguishing it from Destructive actions. The blast radius is medium because misconfigured alarm rules could suppress critical device alerts, but the change itself is not permanent or irreversible.
From the tool's definition Tool name 'update_warning_clean' and description '更新报警清除规则' (Update alarm clearance rule) indicate modification of existing alarm rule configurations.
Attacks that exploit this kind of access
更新报警清除规则. It is categorised as a Write tool in the AIRIOT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AIRIOT MCP Server MCP server in PolicyLayer and add a rule for update_warning_clean: 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 AIRIOT MCP Server. Nothing to install.
update_warning_clean is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_warning_clean 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 update_warning_clean. 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.
update_warning_clean is provided by the AIRIOT MCP Server MCP server (sshwsfc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →