恢复已归档的报警
AI agents use restore_archived_warning 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 restores (un-archives) warnings, which is a reversible modification of data state. It does not permanently delete data (so not Destructive), does not execute arbitrary code (so not Execute), and does not move money (so not Financial). The presence of sibling tools like 'archive_all_warnings' and 'batch_delete_records' confirms this is within a data management context.
From the tool's definition Tool name 'restore_archived_warning' and description '恢复已归档的报警' (restore archived alarm/warning) indicates a state-change operation that reverses a previous archival action, modifying warning records.
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 restore_archived_warning: 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.
restore_archived_warning 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 restore_archived_warning 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 restore_archived_warning. 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.
restore_archived_warning 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 →