Get one team's performance summary for one specific FIRST Robotics Competition (FRC) season. Returns the team's EPA breakdown for that year (start, pre-playoffs, end, max, mean, ranks/percentiles), win/loss/tie record and win rate, count and list of events attended, district points, and award tot...
AI agents call get_team_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 |
|---|---|---|---|
team | integer | Yes | Team number (no prefix), e.g. 86 |
year | integer | Yes | Four-digit year (2002 onwards) |
Parameters from the server's own tool schema.
This is a read-only data retrieval tool that queries historical FIRST Robotics Competition statistics for a specific team and year. It has no side effects, does not modify data, and poses minimal security risk. The tool simply returns aggregated performance metrics and attendance records.
From the tool's definition Tool retrieves performance data: 'Returns the team's EPA breakdown', 'win/loss/tie record', 'list of events attended', 'district points', 'award totals'.
Attacks that exploit this kind of access
Get one team's performance summary for one specific FIRST Robotics Competition (FRC) season. Returns the team's EPA breakdown for that year (start, pre-playoffs, end, max, mean, ranks/percentiles), win/loss/tie record and win rate, count and list of events attended, district points, and award totals. Use this to answer "how did team 2056 do in 2023?", "what was team 254's peak EPA in 2018?", or "how many events did team 1114 attend in 2024?". Requires both team number (integer, no prefix) and a 4-digit year >= 2002. For multi-team or multi-year browsing, use get_team_years. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_team_year accepts 2 parameters: team, year. Required: team, 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_team_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_team_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_team_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_team_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_team_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 →