List all public prediction-market venues covered by Eyewall Markets / Storm, with their slugs, display names, regulatory posture (CFTC-registered DCM, offshore, etc.), posted fee schedules, capability flags (orderbook / AMM / parimutuel), and current ingestion status. Call this first when you nee...
AI agents call storm_list_venues 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 is a straightforward data retrieval operation that queries a catalog of public venues. It has no side effects, makes no modifications to data, and cannot be misused to cause harm beyond potentially accessing public information. The classification as Read is appropriate given the tool's explicit purpose to list reference data. Severity is low because exposure of public venue information carries minimal risk.
From the tool's definition Tool description explicitly states 'List all public prediction-market venues' and 'Reference data only'. The tool retrieves and queries venue information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List all public prediction-market venues covered by Eyewall Markets / Storm, with their slugs, display names, regulatory posture (CFTC-registered DCM, offshore, etc.), posted fee schedules, capability flags (orderbook / AMM / parimutuel), and current ingestion status. Call this first when you need the venue slug to pass to storm_get_market. Reference data only — venue eligibility for any individual user is governed by the venue and the user. 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_venues: 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_venues 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_venues 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_venues. 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_venues 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 →