get_team_availability
Footdigest: a team's active injuries in a competition, player, type, status, and expected return. Give the competition slug and a team name.
This record as markdown: /tools/com-footdigest-footdigest/get-team-availability.md
What get_team_availability does on Footdigest
AI agents call get_team_availability 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 |
|---|---|---|---|
team | string | Yes | Team name, e.g. France. |
competition | string | Yes | Competition slug, e.g. world-cup-2026. |
Parameters from the server's own tool schema.
Why get_team_availability is rated Low
This is a straightforward data retrieval operation that queries injury status information for display/analysis purposes. It has no side effects, cannot modify data, and presents no destructive, financial, or code execution risks. The tool is purely informational, fitting the Read category definition.
From the tool's definition Tool retrieves team injury data ("a team's active injuries in a competition, player, type, status, and expected return") without modifying or deleting any information.
Attacks that exploit this kind of access
The rule that runs get_team_availability 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_team_availability, this is the rule to start with:
get_team_availability 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_team_availability call is checked against it from then on.
Questions about get_team_availability
Footdigest: a team's active injuries in a competition, player, type, status, and expected return. 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_team_availability accepts 2 parameters: team, 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_team_availability: 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_team_availability 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_team_availability 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_team_availability. 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_team_availability 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