market.data.execution · Rekko MCP: Risk & Policy

WHAT IT DOES

What market.data.execution does on Rekko MCP

AI agents invoke market.data.execution to trigger actions in Rekko MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why market.data.execution needs a policy

The tool name 'execution' strongly implies executing trades or orders on prediction market platforms (Kalshi, Polymarket, Robinhood). In financial trading contexts, 'execution' almost universally refers to the act of placing/fulfilling a trade order.

From the tool's definition Tool name 'market.data.execution' on a prediction market platform server that 'enables AI assistants to perform market screening, arbitrage detection, and deep causal analysis to support informed trading decisions.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

market.data.execution Rate-limited

market.data.execution stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "market.data.execution": {
      "limits": [
        {
          "counter": "market.data.execution_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rekko MCP, so you can run agents against it safely.

FAQ

Questions about market.data.execution

What does the market.data.execution tool do? +

market.data.execution. It is categorised as a Execute tool in the Rekko MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on market.data.execution? +

Register the Rekko MCP server in PolicyLayer and add a rule for market.data.execution: 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 Rekko MCP. Nothing to install.

What risk level is market.data.execution? +

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

Can I rate-limit market.data.execution? +

Yes. Add a rate_limit block to the market.data.execution 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 market.data.execution completely? +

Set action: deny in the PolicyLayer policy for market.data.execution. 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 market.data.execution? +

market.data.execution is provided by the Rekko MCP server (rekko-ai/rekko-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.