get_standings
Footdigest: current group standings for a competition, points, goal difference, position, and qualification status per team. Give the competition slug (e.g. "world-cup-2026"), optionally a single group code.
This record as markdown: /tools/com-footdigest-footdigest/get-standings.md
What get_standings does on Footdigest
AI agents call get_standings 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 |
|---|---|---|---|
group | string | — | Optional group code, e.g. A. |
competition | string | Yes | Competition slug, e.g. world-cup-2026. |
Parameters from the server's own tool schema.
Why get_standings is rated Low
get_standings fetches and displays static tournament data (standings, points, positions). It is a pure read operation analogous to querying a sports database. No data is created, modified, deleted, executed, or has financial impact. The low severity reflects that misuse cannot cause harm—an agent querying standings repeatedly poses no risk.
From the tool's definition Tool retrieves 'current group standings for a competition, points, goal difference, position, and qualification status per team'—a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_standings 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_standings, this is the rule to start with:
get_standings 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_standings call is checked against it from then on.
Questions about get_standings
Footdigest: current group standings for a competition, points, goal difference, position, and qualification status per team. Give the competition slug (e.g. "world-cup-2026"), optionally a single group code. It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_standings accepts 2 parameters: group, 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_standings: 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_standings 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_standings 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_standings. 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_standings 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