Get recent transactions (adds, drops, trades) in a league. Pass teamKey to filter to a single team's transactions.
AI agents call get_transactions 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 |
|---|---|---|---|
teamKey | string | — | Filter to this team's transactions |
leagueKey | string | — | League key; defaults to configured league |
Parameters from the server's own tool schema.
This tool retrieves and queries existing transaction data (adds, drops, trades) from a fantasy baseball league. It has no side effects, does not create, modify, or delete data, and does not trigger financial transactions. It is purely informational retrieval, fitting the Read category with low severity.
From the tool's definition Tool description states 'Get recent transactions' with filtering options. The verb 'Get' and action of retrieving transaction history indicates read-only data retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Get recent transactions (adds, drops, trades) in a league. Pass teamKey to filter to a single team's transactions. It is categorised as a Read tool in the Yahoo Fantasy Baseball MCP Server, which means it retrieves data without modifying state.
get_transactions accepts 2 parameters: teamKey, 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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_transactions 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 →