New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_results

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...

SERVERInfersports SOURCEhttps://api.infersports.dev/mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-infersports-infersports/list-results.md

What list_results does on Infersports

AI agents call list_results 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.

ParameterTypeRequiredDescription
date object
team object
limit integer
league object

Parameters from the server's own tool schema.

Why list_results is rated Low

This tool retrieves and queries historical match results from a cache with no side effects, data modification, code execution, or financial impact. It is a pure read operation that returns finished scores and match metadata. The 'limit' parameter and filtering options (date, team, league) confirm it is a standard data retrieval/search function rather than any form of write, execute, or destructive operation.

From the tool's definition Tool description states 'Results-only: each entry is the final score, red cards and finished time (no odds)' and explicitly notes 'Look back at finished-match scores from the 30-day results cache'. The server description also confirms 'Read-only'.

Questions about list_results

What does the list_results tool do? +

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.

What parameters does list_results accept? +

list_results accepts 4 parameters: date, team, limit, league. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_results? +

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.

What risk level is list_results? +

list_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_results? +

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.

How do I block list_results completely? +

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.

What MCP server provides list_results? +

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.

More on Infersports, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Infersports's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.