Look up Statbotics season summary statistics for a single FIRST Robotics Competition (FRC) year. Returns aggregate metrics for the game played that year: EPA (Expected Points Added) percentile breakpoints (mean, median, 75th/90th/95th/99th), score component averages, foul rates, RP (ranking point...
AI agents call get_year to retrieve information from Statbotics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | integer | Yes | Four-digit year (2002 onwards) |
Parameters from the server's own tool schema.
This tool only retrieves and queries pre-computed seasonal statistics from a public sports database. It performs no writes, deletions, code execution, or financial transactions. The blast radius of misuse is minimal — an agent might request irrelevant data but cannot cause harm.
From the tool's definition Tool name 'get_year' and description indicate it 'Look[s] up Statbotics season summary statistics' and 'Returns aggregate metrics' — pure data retrieval with no modification, creation, deletion, or side effects.
Attacks that exploit this kind of access
Look up Statbotics season summary statistics for a single FIRST Robotics Competition (FRC) year. Returns aggregate metrics for the game played that year: EPA (Expected Points Added) percentile breakpoints (mean, median, 75th/90th/95th/99th), score component averages, foul rates, RP (ranking point) rates, and the count of teams, events, and matches recorded. Use this to answer questions like "what was the average score in the 2024 FRC season?", "what EPA put a team in the top 10% in 2019?", or to calibrate per-year scoring before comparing teams across seasons. Data is available for years 2002 onward; pre-2016 seasons have less detail because the EPA model was less granular. For comparing many seasons in one call, use get_years instead. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_year accepts 1 parameter: year. Required: year. The full parameter table on this page comes from the server's own tool schema.
Register the Statbotics MCP server in PolicyLayer and add a rule for get_year: 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 Statbotics. Nothing to install.
get_year 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_year 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_year. 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_year is provided by the Statbotics MCP server (@withinfocus/statbotics-mcp-server). 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 →