[已废弃] 请使用 update_warning 替代。确认告警,将告警状态从active改为acknowledged
AI agents use acknowledge_alarm 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 the state of an alarm record from 'active' to 'acknowledged'. It is a reversible state change/update operation, making it a Write action. It does not delete data, execute code, or involve financial transactions. Severity is medium because misuse could mask active alarms in an IoT platform, potentially hiding real incidents. Confidence slightly reduced because the tool is marked deprecated ([已废弃]).
From the tool's definition 确认告警,将告警状态从active改为acknowledged (changes alarm status from active to acknowledged)
Attacks that exploit this kind of access
[已废弃] 请使用 update_warning 替代。确认告警,将告警状态从active改为acknowledged. 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 acknowledge_alarm: 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.
acknowledge_alarm 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 acknowledge_alarm 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 acknowledge_alarm. 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.
acknowledge_alarm 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 →