kalshi_market_history
Kalshi market history. Returns normalized Kalshi candlesticks for one market from credential-free public market-data JSON.
This record as markdown: /tools/crawlora-mcp/kalshi-market-history.md
What kalshi_market_history does on Crawlora
AI agents call kalshi_market_history 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 |
|---|---|---|---|
end_ts | integer | — | Unix end timestamp in seconds. Defaults to now. |
ticker | string | Yes | Kalshi market ticker |
start_ts | integer | — | Unix start timestamp in seconds. Defaults to 7 days ago. |
series_ticker | string | — | Kalshi series ticker. Defaults to the market ticker prefix before the last dash. |
period_interval | integer | — | Candlestick interval in minutes. Default: 1440. |
include_latest_before_start | boolean | — | Include the latest candle before start_ts when supported upstream. |
Parameters from the server's own tool schema.
Why kalshi_market_history is rated Low
Even though kalshi_market_history 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_market_history 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_market_history, this is the rule to start with:
kalshi_market_history 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_market_history call is checked against it from then on.
Questions about kalshi_market_history
Kalshi market history. Returns normalized Kalshi candlesticks for one market from credential-free public market-data JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
kalshi_market_history accepts 6 parameters: end_ts, ticker, start_ts, series_ticker, period_interval, include_latest_before_start. Required: 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_market_history: 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_market_history 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_market_history 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_market_history. 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_market_history 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