storm_ack_alerts · Storm MCP: Risk & Policy

WHAT IT DOES

What storm_ack_alerts does on Storm

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

WHY IT NEEDS A POLICY

Why storm_ack_alerts needs a policy

This tool modifies server-side state by advancing a persistent acknowledgment cursor, effectively marking alerts as processed and removing them from the inbox view. While it doesn't delete underlying data irreversibly, it mutates a durable server-side cursor that persists across sessions.

From the tool's definition Advance the persistent ack cursor to the given sequence id, removing items at or below it from the api-channel inbox

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

storm_ack_alerts Rate-limited

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

FAQ

Questions about storm_ack_alerts

What does the storm_ack_alerts tool do? +

Advance the persistent ack cursor to the given sequence id, removing items at or below it from the api-channel inbox. Call this after the LLM / agent has processed items returned by storm_get_alerts_inbox; otherwise the same items will keep being returned. Sourced from Eyewall Markets / Storm. The cursor is server-side and survives across MCP sessions. It is categorised as a Write tool in the Storm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on storm_ack_alerts? +

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

What risk level is storm_ack_alerts? +

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

Can I rate-limit storm_ack_alerts? +

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

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

storm_ack_alerts is provided by the Storm MCP server (xch1tbllc/storm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.