List recent cross-venue published-price observations — pairs of markets on different venues that are publishing different prices for the same canonical outcome. Returns rows whose published-price difference net of each venue
AI agents call storm_list_spreads 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 retrieves and lists market spread data across venues—a pure read operation with no side effects. It queries canonical prediction-market information without creating, modifying, executing, or deleting anything. The low severity reflects minimal risk: exposing price spreads cannot directly harm systems or trigger external operations.
From the tool's definition Tool name 'storm_list_spreads' and description 'List recent cross-venue published-price observations' indicate a retrieval operation. The description states it 'Returns rows', confirming data querying with no modification or execution capabilities.
Attacks that exploit this kind of access
List recent cross-venue published-price observations — pairs of markets on different venues that are publishing different prices for the same canonical outcome. Returns rows whose published-price difference net of each venue. 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_spreads: 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_spreads 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_spreads 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_spreads. 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_spreads 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 →