AI agents invoke market.arb.live 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.
This tool executes a computational scan operation across live financial markets. While it does not directly move money (Financial category), it actively triggers an operation whose outcome and side-effects depend on runtime conditions and the AI agent's use of the results. An agent could use arbitrage signals to execute trades immediately, making this an Execute-tier risk.
From the tool's definition Tool description states 'Run a fresh cross-platform arbitrage scan' - the verb 'Run' indicates execution of an operation.
Attacks that exploit this kind of access
Run a fresh cross-platform arbitrage scan (may take 10-30 seconds). 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.
Register the Rekko MCP server in PolicyLayer and add a rule for market.arb.live: 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.
market.arb.live is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the market.arb.live 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 market.arb.live. 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.
market.arb.live 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →