Fetch and aggregate advanced statistics for a single player from multiple authoritative sources: MLB Stats API (standard stats), Baseball Savant (Statcast exit velocity / barrel rate / expected stats), and FanGraphs (WAR, wRC+, K%, BB%, plate discipline). The response includes the league's scorin...
AI agents call analyze_player_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 |
|---|---|---|---|
season | integer | — | Season year, e.g. 2025. Defaults to the current season. |
playerName | string | Yes | Player's full name, e.g. 'Shohei Ohtani' or 'Freddie Freeman' |
Parameters from the server's own tool schema.
This tool retrieves aggregated baseball statistics from external APIs (MLB Stats API, Baseball Savant, FanGraphs) and formats them for decision support. It explicitly serves to inform roster decisions without modifying player assignments or league state. No data is created, modified, deleted, or financial obligations incurred.
From the tool's definition Tool description states it 'Fetch[es] and aggregate[s]' statistics from multiple data sources. Key verbs are 'fetch' and 'aggregate', both retrieval operations.
Attacks that exploit this kind of access
Fetch and aggregate advanced statistics for a single player from multiple authoritative sources: MLB Stats API (standard stats), Baseball Savant (Statcast exit velocity / barrel rate / expected stats), and FanGraphs (WAR, wRC+, K%, BB%, plate discipline). The response includes the league's scoring categories so advice can focus on stats that actually count. Use this before making roster add/drop decisions. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
analyze_player_stats accepts 2 parameters: season, playerName. Required: playerName. 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_player_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_player_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_player_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_player_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_player_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_player_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 →