Fetch advanced stats (Statcast, expected stats, FanGraphs) for a batch of rostered players. Accepts at most 10 players per call via playerKeys — callers should first use get_roster to retrieve all player keys, split them into batches of up to 10, and call this tool once per batch (calls can run i...
AI agents call analyze_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 | — | Roster date as YYYY-MM-DD. Defaults to today. |
season | integer | — | Season year for stat lookup. Defaults to current season. |
teamKey | string | — | Team key, e.g. 431.l.12345.t.2. Defaults to configured team. |
playerKeys | array | — | Subset of roster to fetch, by Yahoo player key or full player name. Max 10. |
Parameters from the server's own tool schema.
This tool retrieves and aggregates read-only fantasy baseball statistics and league information. It does not create, modify, delete, or execute any external operations. The highest capability is fetching and analyzing existing data, making it a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Fetch advanced stats' and 'The response includes the league's scoring categories' — these are query/retrieval operations with no side effects. The tool accepts player keys and returns statistical data only.
Attacks that exploit this kind of access
Fetch advanced stats (Statcast, expected stats, FanGraphs) for a batch of rostered players. Accepts at most 10 players per call via playerKeys — callers should first use get_roster to retrieve all player keys, split them into batches of up to 10, and call this tool once per batch (calls can run in parallel). The response includes the league's scoring categories so advice targets stats that actually matter in this league (e.g. SB if stolen bases count, HLD if holds count). Combine with get_roster to see who is starting or benched. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
analyze_roster_stats accepts 4 parameters: date, season, teamKey, playerKeys. 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 analyze_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.
analyze_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 analyze_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 analyze_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.
analyze_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.
analyze_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 →