scan_slate
Scan today's whole slate in ONE call — each fixture with honest status + value/arb signal. The batch alternative to looping find_match → get_sharp_line per match. Returns every fixture in the filter with its status (finished is excluded from "live"), live score/clock, and a pre-computed value/arb...
This record as markdown: /tools/dev-infersports-infersports/scan-slate.md
What scan_slate does on Infersports
AI agents call scan_slate 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 |
|---|---|---|---|
limit | integer | — | |
sport | object | — | |
format | string | — | |
league | object | — | |
period | object | — | |
status | object | — | |
markets | object | — | |
only_signal | boolean | — | |
min_edge_pct | number | — | |
min_margin_pct | number | — |
Parameters from the server's own tool schema.
Why scan_slate is rated Low
scan_slate queries sporting odds and match data across a slate of fixtures, returning status, scores, and analytical signals. It performs no write, delete, execute, or financial operations—purely data retrieval and display. Severity is low because misuse would at worst return information an agent could act upon, but the tool itself creates no side effects.
From the tool's definition 'Scan today's whole slate in ONE call' and 'DETECTION ONLY / read-only' confirm this tool retrieves and displays fixture data, odds, and value signals without modifying, deleting, or executing operations. The server itself is described as 'Read-only.'
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs scan_slate 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 scan_slate, this is the rule to start with:
scan_slate 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 scan_slate call is checked against it from then on.
Questions about scan_slate
Scan today's whole slate in ONE call — each fixture with honest status + value/arb signal. The batch alternative to looping find_match → get_sharp_line per match. Returns every fixture in the filter with its status (finished is excluded from "live"), live score/clock, and a pre-computed value/arb signal; value/arb matches are sorted to the top and the list is truncated to limit (so truncation drops the quiet ones). Line movement is NOT included (that needs the opening lookup) — drill into a single fixture with get_opening_line. DETECTION ONLY / read-only. Args: sport: optional filter — "football" or "basketball". status: optional filter — "live" | "scheduled" | "finished". league: optional league filter — a name (fuzzy-matched, e.g. "World Cup") or an external id (lg_…). markets: optional — limit the value/arb scan to "1x2"/"asian_handicap"/"totals" (default all). period: optional — "full_time" or "half_time" (default both). min_edge_pct: value threshold for the per-match signal (default 1.0). min_margin_pct: arbitrage threshold for the per-match signal (default 0.0). only_signal: if true, return only fixtures that have a value or arb signal. format: odds format — decimal | hk | malay | american | indonesian | probability. limit: max entries to return, signal-first (default 20, max 100). It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
scan_slate accepts 10 parameters: limit, sport, format, league, period, status, markets, only_signal, min_edge_pct, min_margin_pct. 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 scan_slate: 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.
scan_slate 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 scan_slate 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 scan_slate. 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.
scan_slate 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