Look back at finished-match scores from the 30-day results cache, most-recent-first. Results-only: each entry is the final score, red cards and finished time (no odds). Unlike the live tools, these survive a restart — use it for "what was the score of X?" or "yesterday's results". Args: date: opt...
Part of the Infersports server.
Free to start. No card required.
AI agents call list_results to retrieve information from Infersports without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_results only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"list_results": {}
}
}See the full Infersports policy for all 14 tools.
These attack patterns abuse exactly the kind of access list_results gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Look back at finished-match scores from the 30-day results cache, most-recent-first. Results-only: each entry is the final score, red cards and finished time (no odds). Unlike the live tools, these survive a restart — use it for "what was the score of X?" or "yesterday's results". Args: date: optional UTC kickoff date "YYYY-MM-DD" — the day the match was played. team: optional case-insensitive substring matched against either team name. league: optional case-insensitive substring matched against the league name. limit: max results to return, most-recent-first (1–200, default 50).. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
Register the Infersports MCP server in PolicyLayer and add a rule for list_results: 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.
list_results 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 list_results 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 list_results. 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.
list_results 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.
Deterministic rules across all 14 Infersports tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.