List Statbotics season summary statistics across multiple FIRST Robotics Competition (FRC) years in a single call. Returns the same per-season aggregates as get_year (EPA percentiles, scoring averages, foul/RP rates, counts) but as an array, with optional sorting and pagination. Use this to chart...
AI agents call get_years 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1-1000). Default is 1000. |
metric | string | — | How to sort the returned values. Any column in the table is valid. |
offset | integer | — | Offset from the first result to return. |
ascending | boolean | — | Whether to sort in ascending order. Default is ascending. |
Parameters from the server's own tool schema.
This tool purely retrieves and queries historical FRC competition statistics without any side effects. It reads season-level aggregated data and supports sorting/pagination for analysis purposes. There is no capability to modify data, delete records, execute code, or affect financial systems.
From the tool's definition Tool name is 'get_years' and description states it 'List[s] Statbotics season summary statistics' and 'Returns the same per-season aggregates as get_year'.
Attacks that exploit this kind of access
List Statbotics season summary statistics across multiple FIRST Robotics Competition (FRC) years in a single call. Returns the same per-season aggregates as get_year (EPA percentiles, scoring averages, foul/RP rates, counts) but as an array, with optional sorting and pagination. Use this to chart trends over time, e.g. "how have average match scores evolved from 2002 to today?", "which seasons had the highest top-1% EPA?", or to dump the full season catalog for downstream analysis. Sort with metric (any returned column name, e.g. epa_max, score_mean) and ascending; paginate with limit (1-1000, default 1000) and offset. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_years accepts 4 parameters: limit, metric, offset, ascending. 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_years: 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_years 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_years 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_years. 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_years 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 →