get_schedule
Footdigest: a competition's fixtures with teams, kickoff time, status, score, and stage. Give the competition slug; optionally filter by status (e.g. scheduled, live, finished) and cap with limit.
This record as markdown: /tools/com-footdigest-footdigest/get-schedule.md
What get_schedule does on Footdigest
AI agents call get_schedule 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 | — | Max fixtures to return (default 20, max 100). |
status | string | — | Optional status filter, e.g. finished. |
competition | string | Yes | Competition slug, e.g. world-cup-2026. |
Parameters from the server's own tool schema.
Why get_schedule is rated Low
get_schedule is a data retrieval function that queries and returns football match schedule information. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. The optional filtering parameters (status, limit) are read-only query constraints.
From the tool's definition The tool description explicitly states it retrieves 'a competition's fixtures with teams, kickoff time, status, score, and stage' and allows optional filtering by status and limit.
Attacks that exploit this kind of access
The rule that runs get_schedule 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_schedule, this is the rule to start with:
get_schedule 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_schedule call is checked against it from then on.
Questions about get_schedule
Footdigest: a competition's fixtures with teams, kickoff time, status, score, and stage. Give the competition slug; optionally filter by status (e.g. scheduled, live, finished) and cap with limit. It is categorised as a Read tool in the Footdigest MCP Server, which means it retrieves data without modifying state.
get_schedule accepts 3 parameters: limit, status, 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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