High Risk →

execute_trade

Execute a prediction market trade through TeleKash Broker. Routes your order to the best exchange (Kalshi or Polymarket) based on where the market trades. Or route to native_pool to join TeleKash parimutuel pools — trade alongside Telegram users. Commission: 1% for exchange trades, 5% pool fee fo...

Part of the Telekash server.

execute_trade can trigger actions in Telekash, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TELEKASH →

Free to start. No card required.

AI agents invoke execute_trade to trigger processes or run actions in Telekash. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

execute_trade can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_trade": {
      "limits": [
        {
          "counter": "execute_trade_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Telekash policy for all 29 tools.

Get this rule live on your own Telekash server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TELEKASH →

View all 29 tools →

These attack patterns abuse exactly the kind of access execute_trade gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so execute_trade only ever does what you allow.

SECURE TELEKASH →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the execute_trade tool do? +

Execute a prediction market trade through TeleKash Broker. Routes your order to the best exchange (Kalshi or Polymarket) based on where the market trades. Or route to native_pool to join TeleKash parimutuel pools — trade alongside Telegram users. Commission: 1% for exchange trades, 5% pool fee for native pools (deducted at resolution). Requires: Edge tier API key. Exchange credentials for Kalshi/Polymarket routing. Native pool requires funded agent balance. Native pool benefits: Your USD converts to Stars-equivalent, joining the SAME pool as Telegram mini app users. More participants = deeper liquidity = better odds for everyone. Payout at resolution. Returns: order_id, fill_price, commission, routing details. For native_pool: position_id, pool_composition.. It is categorised as a Execute tool in the Telekash MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_trade? +

Register the Telekash MCP server in PolicyLayer and add a rule for execute_trade: 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.

What risk level is execute_trade? +

execute_trade is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_trade? +

Yes. Add a rate_limit block to the execute_trade 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.

How do I block execute_trade completely? +

Set action: deny in the PolicyLayer policy for execute_trade. 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.

What MCP server provides execute_trade? +

execute_trade 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.

Enforce policy on every Telekash tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.