get_defining_moments
Footdigest: a competition's defining moments, the results that moved teams across the qualification line, most consequential first, with the group table crossings. Give the competition slug; optional limit.
This record as markdown: /tools/com-footdigest-footdigest/get-defining-moments.md
What get_defining_moments does on Footdigest
AI agents call get_defining_moments 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 |
|---|---|---|---|
limit | integer | — | Max moments to return (default 5, max 20). |
competition | string | Yes | Competition slug, e.g. world-cup-2026. |
Parameters from the server's own tool schema.
Why get_defining_moments is rated Low
This tool retrieves and queries historical football competition data (defining moments, qualification transitions, standings crossings). It performs no modifications, deletions, code execution, or financial operations. It is a pure read operation with no side effects, consistent with other sibling tools like get_standings, get_schedule, and get_model_card on the same server.
From the tool's definition Tool name 'get_defining_moments' and description 'a competition's defining moments, the results that moved teams across the qualification line' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_defining_moments 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_defining_moments, this is the rule to start with:
get_defining_moments 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_defining_moments call is checked against it from then on.
Questions about get_defining_moments
Footdigest: a competition's defining moments, the results that moved teams across the qualification line, most consequential first, with the group table crossings. Give the competition slug; optional limit. It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_defining_moments accepts 2 parameters: limit, competition. Required: competition. 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_defining_moments: 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_defining_moments 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_defining_moments 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_defining_moments. 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_defining_moments 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