update_alert_status · Rapid7 MCP: Risk & Policy

WHAT IT DOES

What update_alert_status does on Rapid7

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

WHY IT NEEDS A POLICY

Why update_alert_status needs a policy

This tool modifies existing alert metadata by changing its status to one of three predefined states (open, investigating, closed). This is a reversible Write operation—alert statuses can be changed back, and no data is deleted or destroyed. While it affects security incident tracking in a SIEM, the modification is limited to state management rather than destructive deletion.

From the tool's definition Tool name 'update_alert_status' and description 'Update the status of an InsightIDR alert (open, investigating, or closed)' indicates modification of alert state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_alert_status Rate-limited

update_alert_status 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": {
    "update_alert_status": {
      "limits": [
        {
          "counter": "update_alert_status_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 Rapid7, so you can run agents against it safely.

FAQ

Questions about update_alert_status

What does the update_alert_status tool do? +

Update the status of an InsightIDR alert (open, investigating, or closed). It is categorised as a Write tool in the Rapid7 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_alert_status? +

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

What risk level is update_alert_status? +

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

Can I rate-limit update_alert_status? +

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

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

update_alert_status is provided by the Rapid7 MCP server (solomonneas/rapid7-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.