Get historical probability changes and trend data for a prediction market over time. Returns probability snapshots showing how odds, sentiment, and market consensus have shifted over 1h, 24h, 7d, or 30d. Use for trend analysis, momentum detection, volatility assessment, and understanding how pre...
Part of the Telekash MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_history to retrieve information from Telekash without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_history:
rules:
- action: allowSee the full Telekash policy for all 10 tools.
Agents calling read-class tools like get_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get historical probability changes and trend data for a prediction market over time. Returns probability snapshots showing how odds, sentiment, and market consensus have shifted over 1h, 24h, 7d, or 30d. Use for trend analysis, momentum detection, volatility assessment, and understanding how predictions evolve. Essential for backtesting strategies, identifying probability swings, and spotting market-moving events. Keywords: probability timeline, how odds changed, trend analysis, momentum detection, historical price movement, odds trajectory, price history, probability over time, how has the market moved. It is categorised as a Read tool in the Telekash MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Telekash MCP server.
get_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 get_history rule in your Intercept 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 Intercept policy for get_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.
get_history is provided by the Telekash MCP server (telekash-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept