Get historical performance data for a player
AI agents call get_historical_performance to retrieve information from Fantasy MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries historical data about a player's performance. It has no side effects—it does not create, modify, delete, or execute any operations. It does not move money or trigger financial transactions. While the server context involves sports betting and parlay optimization (which may have financial implications), this specific tool only reads and returns data.
From the tool's definition Tool name 'get_historical_performance' and description 'Get historical performance data for a player' indicate data retrieval with no modification or execution. The action is to query and return existing historical performance metrics.
Attacks that exploit this kind of access
Get historical performance data for a player. It is categorised as a Read tool in the Fantasy MCP MCP Server, which means it retrieves data without modifying state.
Register the Fantasy MCP server in PolicyLayer and add a rule for get_historical_performance: 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 Fantasy MCP. Nothing to install.
get_historical_performance 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_historical_performance 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_historical_performance. 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_historical_performance is provided by the Fantasy MCP server (mattarm/fantasy_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →