kalshi_historical_markets
Kalshi historical markets. Returns normalized settled Kalshi historical market rows from credential-free public market-data JSON. tickers, event_ticker, and series_ticker are mutually exclusive. The mve_filter enum accepts exclude.
This record as markdown: /tools/crawlora-mcp/kalshi-historical-markets.md
What kalshi_historical_markets does on Crawlora
AI agents call kalshi_historical_markets to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Rows to return, default 25, max 1000 |
cursor | string | — | Pagination cursor from a previous Kalshi response |
tickers | string | — | Comma-separated Kalshi market tickers. Mutually exclusive with event_ticker and series_ticker. |
mve_filter | string | — | Multivariate event filter |
event_ticker | string | — | Kalshi event ticker filter. Mutually exclusive with tickers and series_ticker. |
series_ticker | string | — | Kalshi series ticker filter. Mutually exclusive with tickers and event_ticker. |
Parameters from the server's own tool schema.
Why kalshi_historical_markets is rated Low
Even though kalshi_historical_markets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs kalshi_historical_markets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kalshi_historical_markets, this is the rule to start with:
kalshi_historical_markets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every kalshi_historical_markets call is checked against it from then on.
Questions about kalshi_historical_markets
Kalshi historical markets. Returns normalized settled Kalshi historical market rows from credential-free public market-data JSON. tickers, event_ticker, and series_ticker are mutually exclusive. The mve_filter enum accepts exclude. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
kalshi_historical_markets accepts 6 parameters: limit, cursor, tickers, mve_filter, event_ticker, series_ticker. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for kalshi_historical_markets: 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 Crawlora. Nothing to install.
kalshi_historical_markets 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 kalshi_historical_markets 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 kalshi_historical_markets. 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.
kalshi_historical_markets is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue