get_qualification_scenarios
Footdigest: a team's chance of qualifying from its group, and how each remaining group result would move it ("if X beats Y, Z's chances become..."). Seeded and reproducible. Give the competition slug and a team name.
This record as markdown: /tools/com-footdigest-footdigest/get-qualification-scenarios.md
What get_qualification_scenarios does on Footdigest
AI agents call get_qualification_scenarios 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 |
|---|---|---|---|
seed | integer | — | Seed for reproducibility (default 42). |
team | string | Yes | The team whose qualification you're asking about. |
trials | integer | — | Simulated tournaments (default 10000, capped at 50000). |
competition | string | Yes | Competition slug, e.g. world-cup-2026. |
Parameters from the server's own tool schema.
Why get_qualification_scenarios is rated Low
This tool queries and retrieves football prediction scenarios and probabilities. It presents hypothetical outcomes ('if X beats Y') but does not execute those outcomes, modify data, or trigger external operations. The function is purely informational—returning odds and simulations based on competition context (slug and team name).
From the tool's definition Tool name 'get_qualification_scenarios' and description 'a team's chance of qualifying from its group' indicates retrieval of pre-computed predictive data.
Attacks that exploit this kind of access
The rule that runs get_qualification_scenarios 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_qualification_scenarios, this is the rule to start with:
get_qualification_scenarios 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_qualification_scenarios call is checked against it from then on.
Questions about get_qualification_scenarios
Footdigest: a team's chance of qualifying from its group, and how each remaining group result would move it ("if X beats Y, Z's chances become..."). Seeded and reproducible. Give the competition slug and a team name. It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_qualification_scenarios accepts 4 parameters: seed, team, trials, competition. Required: team, 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_qualification_scenarios: 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_qualification_scenarios 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_qualification_scenarios 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_qualification_scenarios. 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_qualification_scenarios 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