get_tournament_odds
Footdigest: each team's chances of qualifying from the group stage, reaching the final, and winning the competition, from a seeded strength-aware Monte Carlo. Pass trials and seed to control and reproduce the run. Identify the competition by its slug (e.g. "world-cup-2026").
This record as markdown: /tools/com-footdigest-footdigest/get-tournament-odds.md
What get_tournament_odds does on Footdigest
AI agents call get_tournament_odds 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). |
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_tournament_odds is rated Low
Even though get_tournament_odds only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_tournament_odds 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_tournament_odds, this is the rule to start with:
get_tournament_odds 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_tournament_odds call is checked against it from then on.
Questions about get_tournament_odds
Footdigest: each team's chances of qualifying from the group stage, reaching the final, and winning the competition, from a seeded strength-aware Monte Carlo. Pass trials and seed to control and reproduce the run. Identify the competition by its slug (e.g. "world-cup-2026"). It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_tournament_odds accepts 3 parameters: seed, trials, 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_tournament_odds: 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_tournament_odds 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_tournament_odds 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_tournament_odds. 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_tournament_odds 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