get_result
Get the cached final result for ONE finished match by event id. Returns the final score, red cards and finished time. status is "found" or "not_found" (the match isn't in the 30-day cache). Results-only — no odds. Args: event_id: event id (e.g. "evt_…") from find_match / list_results.
This record as markdown: /tools/dev-infersports-infersports/get-result.md
What get_result does on Infersports
AI agents call get_result 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 |
|---|---|---|---|
event_id | string | Yes |
Parameters from the server's own tool schema.
Why get_result is rated Low
This tool retrieves historical sports match results from a cache without any ability to modify, delete, or execute operations. It is a pure read operation querying completed match information. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose past match data already available in the public 30-day cache.
From the tool's definition Tool description states 'Get the cached final result for ONE finished match' and 'Results-only — no odds.' Returns only historical match data: 'final score, red cards and finished time.' No modification, deletion, or side effects mentioned.
Attacks that exploit this kind of access
The rule that runs get_result 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 get_result, this is the rule to start with:
get_result 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 get_result call is checked against it from then on.
Questions about get_result
Get the cached final result for ONE finished match by event id. Returns the final score, red cards and finished time. status is "found" or "not_found" (the match isn't in the 30-day cache). Results-only — no odds. Args: event_id: event id (e.g. "evt_…") from find_match / list_results. It is categorised as a Read tool in the Infersports MCP Server, which means it retrieves data without modifying state.
get_result accepts 1 parameter: event_id. Required: event_id. 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 get_result: 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.
get_result 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 get_result 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 get_result. 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.
get_result 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