simulate
Footdigest: run the seeded Monte Carlo over a competition's group stage and return each team's advancement probabilities. Pass trials and seed to control and reproduce the run; the same inputs always return the same numbers. Identify the competition by its slug (e.g. "world-cup-2026").
This record as markdown: /tools/com-footdigest-footdigest/simulate.md
What simulate does on Footdigest
AI agents invoke simulate to trigger actions in Footdigest. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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 simulate is rated High
Although the tool performs a read-only simulation (it returns probabilities without modifying persistent state), it crosses into Execute territory because it runs a non-trivial algorithmic operation (Monte Carlo simulation) whose computational cost and results depend on user-supplied parameters. The tool is deterministic and safe (same inputs yield same outputs), limiting severity to medium rather than high.
From the tool's definition The tool 'simulate' uses language that indicates code execution: 'run the seeded Monte Carlo' explicitly states it runs a computational procedure.
Attacks that exploit this kind of access
The rule that runs simulate 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 simulate, this is the rule to start with:
simulate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 simulate call is checked against it from then on.
Questions about simulate
Footdigest: run the seeded Monte Carlo over a competition's group stage and return each team's advancement probabilities. Pass trials and seed to control and reproduce the run; the same inputs always return the same numbers. Identify the competition by its slug (e.g. "world-cup-2026"). It is categorised as a Execute tool in the Footdigest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
simulate 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 simulate: 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.
simulate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate 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 simulate. 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.
simulate 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.
Across the catalogue