find_arbitrage
Find cross-book arbitrage in a fixture — a guaranteed-profit price split — in ONE call. Resolves the fixture, then for each market/line takes the best price per outcome across books; when the inverse prices sum to < 1 there is a locked margin regardless of result. Reports the margin % and which b...
This record as markdown: /tools/dev-infersports-infersports/find-arbitrage.md
What find_arbitrage does on Infersports
AI agents call find_arbitrage to retrieve information from Infersports without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | object | — | |
query | string | Yes | |
sport | object | — | |
format | string | — | |
period | object | — | |
markets | object | — | |
min_margin_pct | number | — |
Parameters from the server's own tool schema.
Why find_arbitrage is rated Low
find_arbitrage purely queries and analyzes betting odds across multiple bookmakers to detect arbitrage opportunities. It reads data, performs calculations, and reports results with no side effects, state changes, or financial actions. The explicit 'read-only' designation and lack of bet execution capabilities confirm Read category.
From the tool's definition Tool description explicitly states 'DETECTION ONLY: no stake sizing, no bet links — InferSports is read-only' and 'Resolves the fixture, then for each market/line takes the best price per outcome across books...Reports the margin %'.
Attacks that exploit this kind of access
The rule that runs find_arbitrage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infersports, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_arbitrage, this is the rule to start with:
find_arbitrage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Infersports, apply this rule, and every find_arbitrage call is checked against it from then on.
Questions about find_arbitrage
Find cross-book arbitrage in a fixture — a guaranteed-profit price split — in ONE call. Resolves the fixture, then for each market/line takes the best price per outcome across books; when the inverse prices sum to < 1 there is a locked margin regardless of result. Reports the margin % and which book holds each leg (legs must come from ≥2 distinct books). DETECTION ONLY: no stake sizing, no bet links — InferSports is read-only. Args: query: natural-language fixture, e.g. "Netherlands vs Algeria" or a single team. markets: optional filter — any of "1x2", "asian_handicap", "totals" (default: all). period: optional — "full_time" or "half_time" (default: both). min_margin_pct: only report opportunities with at least this guaranteed margin (default 0). format: odds format — decimal | hk | malay | american | indonesian | probability. sport: optional filter — "football" or "basketball". date: optional UTC date "YYYY-MM-DD" to disambiguate same-name fixtures. On an ambiguous query, status is "ambiguous" and ask_user carries a prompt — do not guess. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
find_arbitrage accepts 7 parameters: date, query, sport, format, period, markets, min_margin_pct. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Infersports MCP server in PolicyLayer and add a rule for find_arbitrage: 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 Infersports. Nothing to install.
find_arbitrage 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 find_arbitrage 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 find_arbitrage. 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.
find_arbitrage is provided by the Infersports MCP server (https://api.infersports.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infersports, and thousands of servers like it.
This server
Across the catalogue