kalshi_events
Kalshi events. Returns normalized Kalshi event rows from credential-free public market-data JSON.
This record as markdown: /tools/crawlora-mcp/kalshi-events.md
What kalshi_events does on Crawlora
AI agents call kalshi_events 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 200 |
cursor | string | — | Pagination cursor from a previous Kalshi response |
status | string | — | Event status filter |
category | string | — | Kalshi category filter |
min_close_ts | integer | — | Minimum event close Unix timestamp in seconds |
series_ticker | string | — | Kalshi series ticker filter |
min_updated_ts | integer | — | Minimum event update Unix timestamp in seconds |
with_milestones | boolean | — | Include event milestones when supported upstream |
with_nested_markets | boolean | — | Include nested market rows when supported upstream |
Parameters from the server's own tool schema.
Why kalshi_events is rated Low
Even though kalshi_events 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_events 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_events, this is the rule to start with:
kalshi_events 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_events call is checked against it from then on.
Questions about kalshi_events
Kalshi events. Returns normalized Kalshi event rows 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_events accepts 9 parameters: limit, cursor, status, category, min_close_ts, series_ticker, min_updated_ts, with_milestones, with_nested_markets. 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_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 Crawlora. Nothing to install.
kalshi_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 kalshi_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 kalshi_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.
kalshi_events 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