archive_alerts · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_alerts does on CloudStack MCP Server

AI agents use archive_alerts to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

WHY IT NEEDS A POLICY

Why archive_alerts needs a policy

Archiving alerts changes their state from active to archived, which is a reversible modification of data. This is a Write operation rather than Destructive because archiving is not permanent deletion and can typically be undone by un-archiving. The blast radius is low since it only affects alert visibility/organization without impacting infrastructure, services, or data integrity.

From the tool's definition Tool name 'archive_alerts' and description 'Archive system alerts' indicate a write operation that modifies alert status/state by archiving (moving alerts into an archived state).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_alerts Rate-limited

archive_alerts 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_alerts": {
      "limits": [
        {
          "counter": "archive_alerts_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 CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_alerts

What does the archive_alerts tool do? +

Archive system alerts. It is categorised as a Write tool in the CloudStack 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_alerts? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for archive_alerts: 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 CloudStack MCP Server. Nothing to install.

What risk level is archive_alerts? +

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

Can I rate-limit archive_alerts? +

Yes. Add a rate_limit block to the archive_alerts 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_alerts completely? +

Set action: deny in the PolicyLayer policy for archive_alerts. 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_alerts? +

archive_alerts is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.