archive_all_warnings · AIRIOT MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_all_warnings does on AIRIOT MCP Server

AI agents use archive_all_warnings 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.

WHY IT NEEDS A POLICY

Why archive_all_warnings needs a policy

Archiving is a Write operation—it modifies the state of warnings (marking them as archived) but does not irreversibly delete data. The 'all' scope and one-click nature pose medium severity risk if triggered incorrectly (potential loss of visibility into many warnings), but the operation is reversible.

From the tool's definition Tool name 'archive_all_warnings' and description '一键归档所有符合条件的报警' (one-click archive all warnings matching criteria) indicates a bulk modification operation that marks/archives warnings rather than deleting them. This is reversible state change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_all_warnings Rate-limited

archive_all_warnings stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_all_warnings": {
      "limits": [
        {
          "counter": "archive_all_warnings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AIRIOT MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_all_warnings

What does the archive_all_warnings tool do? +

一键归档所有符合条件的报警. 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.

How do I enforce a policy on archive_all_warnings? +

Register the AIRIOT MCP Server MCP server in PolicyLayer and add a rule for archive_all_warnings: 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.

What risk level is archive_all_warnings? +

archive_all_warnings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archive_all_warnings? +

Yes. Add a rate_limit block to the archive_all_warnings 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.

How do I block archive_all_warnings completely? +

Set action: deny in the PolicyLayer policy for archive_all_warnings. 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.

What MCP server provides archive_all_warnings? +

archive_all_warnings 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.