Get stats, standings, and matchups for every team in a league. Pass explicit teamKeys to limit the set, otherwise all teams in the league are fetched.
AI agents call get_teams to retrieve information from Yahoo Fantasy Baseball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamKeys | array | — | Specific team keys; defaults to all teams in the league |
leagueKey | string | — | League key, e.g. 431.l.12345 |
Parameters from the server's own tool schema.
This tool retrieves and queries fantasy baseball league data (statistics, standings, matchup information). It performs no data modification, deletion, code execution, or financial transactions. The 'Get' verb and the read-only nature of retrieving stats and standings clearly indicate a Read category tool.
From the tool's definition Tool description states it 'Get stats, standings, and matchups for every team in a league' - purely retrieval operations with no modification, deletion, or execution of external commands. Returns data without side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get stats, standings, and matchups for every team in a league. Pass explicit teamKeys to limit the set, otherwise all teams in the league are fetched. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
get_teams accepts 2 parameters: teamKeys, leagueKey. The full parameter table on this page comes from the server's own tool schema.
Register the Yahoo Fantasy Baseball MCP server in PolicyLayer and add a rule for get_teams: 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 Yahoo Fantasy Baseball. Nothing to install.
get_teams 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_teams 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_teams. 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_teams is provided by the Yahoo Fantasy Baseball MCP server (yahoo-fantasy-baseball-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_teams is one line of Yahoo Fantasy Baseball's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →