List canonical prediction-market events (questions/topics) tracked by Eyewall Markets / Storm across the public venues it covers (Kalshi, Polymarket, Manifold, ForecastEx, and others). Use this to discover what events exist before drilling into a specific event with storm_get_event. Supports filt...
AI agents call storm_list_events to retrieve information from Storm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve and filter event data from prediction markets. There are no modifications, deletions, executions, or financial transactions involved. The tool simply returns information about events to enable discovery, making it a straightforward Read category operation with low severity—misuse would only expose available market data without enabling harmful actions.
From the tool's definition Tool description explicitly states 'List canonical prediction-market events' and 'Use this to discover what events exist before drilling into a specific event'.
Attacks that exploit this kind of access
List canonical prediction-market events (questions/topics) tracked by Eyewall Markets / Storm across the public venues it covers (Kalshi, Polymarket, Manifold, ForecastEx, and others). Use this to discover what events exist before drilling into a specific event with storm_get_event. Supports filtering by category (e.g. It is categorised as a Read tool in the Storm MCP Server, which means it retrieves data without modifying state.
Register the Storm MCP server in PolicyLayer and add a rule for storm_list_events: 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.
storm_list_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the storm_list_events 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.
Set action: deny in the PolicyLayer policy for storm_list_events. 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.
storm_list_events 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →