get_match_brief
Footdigest: the AI-generated brief for a match, the pre-match five-lens brief, the post-match recap, and event impacts, sourced from Footdigest's engine. Ask by match_id; optional locale (en or fr).
This record as markdown: /tools/com-footdigest-footdigest/get-match-brief.md
What get_match_brief does on Footdigest
AI agents call get_match_brief 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 |
|---|---|---|---|
locale | string | — | Language: en (default) or fr. |
match_id | integer | Yes | Fixture id (from get_schedule). |
Parameters from the server's own tool schema.
Why get_match_brief is rated Low
This is a read-only retrieval tool that queries and returns football match analysis data. It has no side effects, does not execute code or external operations, does not modify or delete data, and involves no financial transactions. The blast radius of misuse is minimal—an agent could only retrieve unwanted match data, which presents no meaningful security risk.
From the tool's definition Tool retrieves match briefs, pre-match analysis, post-match recaps, and event impacts. Operations are queries by match_id with optional locale parameter. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs get_match_brief 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_brief, this is the rule to start with:
get_match_brief 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_brief call is checked against it from then on.
Questions about get_match_brief
Footdigest: the AI-generated brief for a match, the pre-match five-lens brief, the post-match recap, and event impacts, sourced from Footdigest's engine. Ask by match_id; optional locale (en or fr). It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_match_brief accepts 2 parameters: locale, 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_brief: 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_brief 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_brief 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_brief. 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_brief 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