Get a team's roster with each player's Yahoo stats for a given date. Like get_roster but heavier — use get_roster when you only need slots/status, or analyze_roster_stats for advanced (Statcast/FanGraphs) stats. Defaults to the configured team and today's date.
AI agents call get_roster_stats 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 |
|---|---|---|---|
date | string | — | Date as YYYY-MM-DD; defaults to today |
teamKey | string | — | Team key, e.g. 431.l.12345.t.2 |
Parameters from the server's own tool schema.
This tool retrieves and queries roster statistics data with no side effects. It is a read operation that fetches information about players and their stats from Yahoo Fantasy Baseball. There is no capability to modify, delete, or execute external operations. The low severity reflects minimal risk even if misused by an agent, as it only accesses existing statistical data.
From the tool's definition Tool description states 'Get a team's roster with each player's Yahoo stats for a given date.' The verb 'Get' and the phrase 'retrieves' data without modification indicate a read-only operation.
Attacks that exploit this kind of access
Get a team's roster with each player's Yahoo stats for a given date. Like get_roster but heavier — use get_roster when you only need slots/status, or analyze_roster_stats for advanced (Statcast/FanGraphs) stats. Defaults to the configured team and today's date. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
get_roster_stats accepts 2 parameters: date, teamKey. 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_roster_stats: 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_roster_stats 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_roster_stats 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_roster_stats. 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_roster_stats 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_roster_stats 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 →