// SCAN REPORT

Storm

7 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 03/07/2026

How to control Storm ↓

TOOL MAP

What Storm exposes to your agents

Read (6) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Storm tools

Write · Medium storm_ack_alerts This tool modifies server-side state by advancing a persistent acknowledgment cursor, effectively marking alerts as processed and removing them from the inbox view.

1 of Storm's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Storm

PolicyLayer is an MCP gateway — it sits between your AI agents and Storm, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "storm_ack_alerts": {
    "limits": [
      {
        "counter": "storm_ack_alerts_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "storm_get_alerts_inbox": {
    "limits": [
      {
        "counter": "storm_get_alerts_inbox_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Storm — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON STORM →

Instant setup, no code required.

FULL CATALOGUE

All 7 Storm tools

WRITE 1 tools

Write storm_ack_alerts Advance the persistent ack cursor to the given sequence id, removing items at or below it from the api-channel

READ 6 tools

Read storm_get_alerts_inbox Poll the subscriber Read storm_get_event Fetch a single canonical event by its Storm slug, including the full set of cross-venue markets attached to th Read storm_get_market Fetch the canonical Storm view of a single market on a specific venue, including the venue Read storm_list_events List canonical prediction-market events (questions/topics) tracked by Eyewall Markets / Storm across the publi Read storm_list_spreads List recent cross-venue published-price observations — pairs of markets on different venues that are publishin Read storm_list_venues List all public prediction-market venues covered by Eyewall Markets / Storm, with their slugs, display names,

FAQ

Questions about Storm

How do I prevent bulk modifications through Storm? +

The Storm server has 1 write tools including storm_ack_alerts. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Storm.

How many tools does the Storm MCP server expose? +

7 tools across 1 categories: Read. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Storm? +

Register the Storm MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Storm tool call.

Deterministic rules across all 7 Storm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON STORM →

Instant setup, no code required.

7 Storm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.