A team's schedule — upcoming and recent games with dates, opponents, and (for finished games) scores and result. PREFER for "when do the Lakers play next", "<team>'s schedule", "<team> recent results". Get the numeric team_id from get_teams. Common sport/league pairs: football/nfl, football/colle...
AI agents call get_team_schedule to retrieve information from Mcp Espn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sport | string | Yes | Sport, e.g. 'basketball'. |
league | string | Yes | League slug, e.g. 'nba'. |
team_id | string | Yes | Numeric ESPN team id (from get_teams), e.g. "13" for the Lakers. |
Parameters from the server's own tool schema.
This tool queries and returns sports schedule information from ESPN's public API. It has no side effects, does not modify any data, and does not execute code or trigger external operations beyond data retrieval. It is a straightforward read-only operation that fetches historical and upcoming game schedules. Minimal security risk even if misused by an agent.
From the tool's definition Tool retrieves schedule data — 'upcoming and recent games with dates, opponents, and (for finished games) scores and result'. Returns historical and future game information without modification.
Attacks that exploit this kind of access
A team's schedule — upcoming and recent games with dates, opponents, and (for finished games) scores and result. PREFER for "when do the Lakers play next", "<team>'s schedule", "<team> recent results". Get the numeric team_id from get_teams. Common sport/league pairs: football/nfl, football/college-football, basketball/nba, basketball/wnba, basketball/mens-college-basketball, baseball/mlb, hockey/nhl, soccer/eng.1 (Premier League), soccer/usa.1 (MLS), soccer/esp.1 (La Liga), soccer/uefa.champions (Champions League). It is categorised as a Read tool in the Mcp Espn MCP Server, which means it retrieves data without modifying state.
get_team_schedule accepts 3 parameters: sport, league, team_id. Required: sport, league, team_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Espn MCP server in PolicyLayer and add a rule for get_team_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 Mcp Espn. Nothing to install.
get_team_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_team_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_team_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_team_schedule is provided by the Mcp Espn MCP server (pipeworx-io/mcp-espn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →