Get a structured pre-computed trading signal for any prediction market — TeleKash Probability Format (TPF). Combines probability, confidence, sentiment, noise filter, and cross-source data into one actionable signal. This is the complete intelligence package for autonomous agents. Returns: - prob...
Part of the Telekash server.
Free to start. No card required.
AI agents call get_signal 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_signal 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_signal": {}
}
}See the full Telekash policy for all 29 tools.
These attack patterns abuse exactly the kind of access get_signal gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get a structured pre-computed trading signal for any prediction market — TeleKash Probability Format (TPF). Combines probability, confidence, sentiment, noise filter, and cross-source data into one actionable signal. This is the complete intelligence package for autonomous agents. Returns: - probability with confidence grade (HIGH/MEDIUM/LOW/VERY_LOW) - sentiment score with recommendation (bullish/bearish/neutral) - noise filter (signal/weak/noise) — is this momentum real or random walk? - cross-source spread (if market exists on multiple exchanges) - actionable verdict: STRONG_BUY / BUY / HOLD / SELL / STRONG_SELL / NO_SIGNAL Use this as the single entry point when an agent needs to make a trade decision. One call replaces get_probability + get_sentiment + get_history + compare_sources.. It is categorised as a Read tool in the Telekash MCP Server, which means it retrieves data without modifying state.
Register the Telekash MCP server in PolicyLayer and add a rule for get_signal: 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.
get_signal 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_signal 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 get_signal. 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_signal 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.