Export structured prediction market data in bulk. Historical probabilities, resolution outcomes, market catalogs, and arbitrage history. Types: probability_history (how odds changed over time), resolution_outcomes (how markets resolved), market_catalog (all active markets with metadata), arbitrag...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Telekash server.
Free to start. No card required.
AI agents use export_data to create or modify resources in Telekash. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call export_data repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Telekash.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"export_data": {
"limits": [
{
"counter": "export_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Telekash policy for all 29 tools.
These attack patterns abuse exactly the kind of access export_data gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Export structured prediction market data in bulk. Historical probabilities, resolution outcomes, market catalogs, and arbitrage history. Types: probability_history (how odds changed over time), resolution_outcomes (how markets resolved), market_catalog (all active markets with metadata), arbitrage_history (cross-source price gaps). Returns structured JSON or CSV format. Max 1000 records per export. Keywords: bulk data export, historical data, prediction dataset, market data feed, data licensing, research data, backtesting data, probability timeseries. It is categorised as a Write tool in the Telekash MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telekash MCP server in PolicyLayer and add a rule for export_data: 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 Telekash. Nothing to install.
export_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_data 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 export_data. 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.
export_data is provided by the Telekash MCP server (telekash-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Telekash tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.