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).
This record as markdown: /tools/com-footdigest-footdigest/get-match.md
What get_match does on Footdigest
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
match_id | integer | Yes | Fixture id, e.g. from get_schedule. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_match safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Footdigest, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_match, this is the rule to start with:
get_match 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 Footdigest, apply this rule, and every get_match call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_match accepts 1 parameter: match_id. Required: match_id. The full parameter table on this page comes from the server's own tool schema.
Register the Footdigest MCP server in PolicyLayer and add a rule for get_match: 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 Footdigest. Nothing to install.
get_match 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_match 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_match. 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_match is provided by the Footdigest MCP server (https://footdigest.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Footdigest, and thousands of servers like it.
This server
Across the catalogue