Register a webhook alert for prediction market events. When the condition is met, TeleKash POSTs TPF-formatted data to your callback URL. Available conditions: - probability_crosses_above: Triggered when market probability rises above threshold (e.g., 70%) - probability_crosses_below: Triggered w...
Part of the Telekash server.
Free to start. No card required.
AI agents use register_alert 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 register_alert 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": {
"register_alert": {
"limits": [
{
"counter": "register_alert_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 register_alert 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.
Register a webhook alert for prediction market events. When the condition is met, TeleKash POSTs TPF-formatted data to your callback URL. Available conditions: - probability_crosses_above: Triggered when market probability rises above threshold (e.g., 70%) - probability_crosses_below: Triggered when market probability falls below threshold (e.g., 30%) - mispricing_detected: Triggered when cross-source spread exceeds threshold (e.g., 5%) - volume_spike: Triggered when 1h volume exceeds threshold multiple of average - resolution: Triggered when market resolves (no threshold needed) - divergence_detected: Triggered when any source disagrees beyond threshold Alerts auto-expire after 30 days. Cooldown prevents duplicate triggers (default: 60 min). Event-driven, not polling — your agent sleeps until we wake it up.. 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 register_alert: 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.
register_alert 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 register_alert 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 register_alert. 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.
register_alert 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.