Generate a free TeleKash API key for rate-limited access to prediction market intelligence. Free tier: 100 calls/day, 7 core tools (probability, markets, search, history, sentiment, stats, trending). Calibration tier ($0.01/query): 1,000 calls/day + arbitrage, divergence, and performance trackin...
Part of the Telekash MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use generate_api_key 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 generate_api_key repeatedly, creating or modifying resources faster than any human could review. Intercept'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.
tools:
generate_api_key:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Telekash policy for all 10 tools.
Agents calling write-class tools like generate_api_key have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Generate a free TeleKash API key for rate-limited access to prediction market intelligence. Free tier: 100 calls/day, 7 core tools (probability, markets, search, history, sentiment, stats, trending). Calibration tier ($0.01/query): 1,000 calls/day + arbitrage, divergence, and performance tracking tools. Edge tier ($0.05/query): Unlimited + TPF signals, Kelly sizing, and market creation. The API key is returned ONCE — save it immediately. Set it as TELEKASH_API_KEY environment variable.. 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.
Add a rule in your Intercept YAML policy under the tools section for generate_api_key. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Telekash MCP server.
generate_api_key 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 generate_api_key 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 generate_api_key. 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.
generate_api_key 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