// SCAN REPORT

Rekko MCP

34 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

4 can modify or destroy data

30 read-only

34 tools total

Community server · catalogue entry verified 30/06/2026

How to control Rekko MCP ↓

TOOL MAP

What Rekko MCP exposes to your agents

Read (30) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Rekko MCP tools

Destructive · Medium trade.hooks.delete The tool permanently removes a registered webhook, which is an irreversible destructive action. Execute · High market.events.analyze This tool executes (not merely reads) analytical operations that generate market intelligence and strategy signals. Execute · High market.arb.live This tool executes a computational scan operation across live financial markets. Execute · High market.data.execution The tool name 'execution' strongly implies executing trades or orders on prediction market platforms (Kalshi, Polymarket, Robinhood).

4 of Rekko MCP's 34 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Rekko MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Rekko MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "trade.hooks.delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "analytics.performance": {
    "limits": [
      {
        "counter": "analytics.performance_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rekko MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REKKO →

Instant setup, no code required.

FULL CATALOGUE

All 34 Rekko MCP tools

DESTRUCTIVE 1 tools

Destructive trade.hooks.delete Remove a registered webhook.

EXECUTE 3 tools

Execute market.arb.live Run a fresh cross-platform arbitrage scan (may take 10-30 seconds). Execute market.data.execution market.data.execution Execute market.events.analyze Trigger an AI analysis of an entire prediction market event (all sub-markets).

READ 30 tools

Read analytics.performance Get aggregate trading performance statistics — win rate, ROI, total P&L. Read analytics.report analytics.report Read help.quickstart Get a quickstart code snippet to make your first Rekko API call. Read market.arb.correlation market.arb.correlation Read market.arb.get Get cross-platform arbitrage opportunities between Kalshi and Polymarket (cached). Read market.data.get market.data.get Read market.data.history market.data.history Read market.data.list market.data.list Read market.data.resolution market.data.resolution Read market.data.screen market.data.screen Read market.data.search market.data.search Read market.events.analysis market.events.analysis Read market.events.correlation Get cross-market correlation analysis within a prediction market event. Read market.events.get market.events.get Read market.events.list market.events.list Read market.events.markets List all individual outcome markets within a prediction market event. Read market.events.probability_map Get probability estimates for all sub-markets within an event. Read market.events.search market.events.search Read research.pipe.get research.pipe.get Read research.pipe.list List recent analyses with summary information. Read research.pipe.start research.pipe.start Read research.pipe.status research.pipe.status Read research.signal.calibration research.signal.calibration Read research.signal.consensus research.signal.consensus Read research.signal.portfolio research.signal.portfolio Read research.signal.signal research.signal.signal Read research.signal.what_if research.signal.what_if Read trade.hooks.create trade.hooks.create Read trade.hooks.list List registered webhooks.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Rekko MCP

Can an AI agent delete data through the Rekko MCP server? +

Yes. The Rekko MCP server exposes 1 destructive tools including trade.hooks.delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Rekko MCP server expose? +

34 tools across 3 categories: Destructive, Execute, Read. 30 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Rekko MCP? +

Register the Rekko MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rekko MCP tool call.

Deterministic rules across all 34 Rekko MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REKKO →

Instant setup, no code required.

34 Rekko MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.