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

Agent View of the PolicyLayer registry record for `get_result`. HTML page: https://policylayer.com/tools/dev-infersports-infersports/get-result

## Facts

- Tool: `get_result`
- Server: Infersports (`https://api.infersports.dev/mcp`) — https://policylayer.com/tools/dev-infersports-infersports.md
- Homepage: https://github.com/https://api.infersports.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `event_id` | string | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_result",
    "arguments": {
      "event_id": "<event_id>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Infersports:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_result": {}
  }
}
```

## Other tools on Infersports (16)

- `compare_lines` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-lines.md
- `compare_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/compare-prob.md
- `explain_handicap` — Read — https://policylayer.com/tools/dev-infersports-infersports/explain-handicap.md
- `find_arbitrage` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-arbitrage.md
- `find_match` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-match.md
- `find_value` — Read — https://policylayer.com/tools/dev-infersports-infersports/find-value.md
- `get_match_odds` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-match-odds.md
- `get_opening_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-opening-line.md
- `get_sharp_line` — Read — https://policylayer.com/tools/dev-infersports-infersports/get-sharp-line.md
- `list_bookmakers` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-bookmakers.md
- `list_events` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-events.md
- `list_results` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-results.md
- `list_today_matches` — Read — https://policylayer.com/tools/dev-infersports-infersports/list-today-matches.md
- `match_info` — Read — https://policylayer.com/tools/dev-infersports-infersports/match-info.md
- `scan_slate` — Read — https://policylayer.com/tools/dev-infersports-infersports/scan-slate.md
- `score_prob` — Read — https://policylayer.com/tools/dev-infersports-infersports/score-prob.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-infersports-infersports · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-infersports-infersports