get_head_to_head
Footdigest: the all-time head-to-head record between two men's national teams from the historical results dataset, wins, draws, goals, recent meetings, and penalty shootouts. Ask by team names.
This record as markdown: /tools/com-footdigest-footdigest/get-head-to-head.md
What get_head_to_head does on Footdigest
AI agents call get_head_to_head 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 | — | Recent meetings to include (default 5, max 20). |
team1 | string | Yes | First team name, e.g. France. |
team2 | string | Yes | Second team name, e.g. Spain. |
Parameters from the server's own tool schema.
Why get_head_to_head is rated Low
The tool performs data retrieval operations only. It queries historical football statistics and records without creating, modifying, executing code, or causing any destructive actions. This is a straightforward read operation consistent with other sibling tools on the server (get_bracket, get_standings, get_schedule, etc.) that all retrieve pre-computed or stored information.
From the tool's definition Tool retrieves historical head-to-head records, wins, draws, goals, and recent meetings between teams—all read-only queries with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_head_to_head 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_head_to_head, this is the rule to start with:
get_head_to_head 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_head_to_head call is checked against it from then on.
Questions about get_head_to_head
Footdigest: the all-time head-to-head record between two men's national teams from the historical results dataset, wins, draws, goals, recent meetings, and penalty shootouts. Ask by team names. It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_head_to_head accepts 3 parameters: limit, team1, team2. Required: team1, team2. 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_head_to_head: 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_head_to_head 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_head_to_head 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_head_to_head. 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_head_to_head 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