# get_match

Footdigest: one fixture in detail, teams, status, kickoff, score, stage, venue, and the event timeline (goals, cards, subs). Ask by match_id (from get_schedule).

Agent View of the PolicyLayer registry record for `get_match`. HTML page: https://policylayer.com/tools/com-footdigest-footdigest/get-match

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `match_id` | integer | yes | Fixture id, e.g. from get_schedule. |

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_match",
    "arguments": {
      "match_id": 0
    }
  }
}
```

## Why get_match is rated Low

This tool queries and returns structured football match data without any side effects. It is purely informational, returning pre-computed or stored match information (scores, timelines, venue details) without the ability to create, modify, or delete data. No external operations are triggered. Classified as Read with low severity due to the benign nature of sports statistics exposure.

From the tool's own definition: "Tool retrieves match details (teams, status, kickoff, score, stage, venue, event timeline) by match_id parameter with no indication of modification or deletion capabilities."

## Use case

AI agents call get_match to retrieve information from Footdigest 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 Footdigest:

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

## Other tools on Footdigest (13)

- `simulate` — Execute — https://policylayer.com/tools/com-footdigest-footdigest/simulate.md
- `get_bracket` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-bracket.md
- `get_defining_moments` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-defining-moments.md
- `get_head_to_head` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-head-to-head.md
- `get_match_brief` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-match-brief.md
- `get_match_probabilities` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-match-probabilities.md
- `get_model_card` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-model-card.md
- `get_qualification_scenarios` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-qualification-scenarios.md
- `get_schedule` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-schedule.md
- `get_standings` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-standings.md
- `get_suspension_watch` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-suspension-watch.md
- `get_team_availability` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-team-availability.md
- `get_tournament_odds` — Read — https://policylayer.com/tools/com-footdigest-footdigest/get-tournament-odds.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=com-footdigest-footdigest · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-footdigest-footdigest