List FIRST Robotics Competition (FRC) team-event records with flexible filters. Each row represents one team's performance at one event (rank, record, EPA, awards). Filter any combination of team (one team across all events), year, event (all teams at one event - great for getting an event's full...
AI agents call get_team_events 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 | — | Team number (no prefix), e.g. 86 |
type | string | — | One of: regional, district, district_cmp, champs_div, einstein, or offseason. |
week | integer | — | Week of the competition season. 8 is CMP. |
year | integer | — | Four-digit year (2002 onwards) |
event | string | — | Event key, e.g. 2024flor |
limit | integer | — | Maximum number of results to return (1-1000). Default is 1000. |
state | string | — | Capitalized two-letter state code, e.g. NC. |
metric | string | — | How to sort the returned values. Any column in the table is valid. |
offset | integer | — | Offset from the first result to return. |
country | string | — | Capitalized country name, e.g. USA or Canada. |
district | string | — | District abbreviation. One of: ca, fch, fim, fin, fit, fma, fnc, fsc, isr, ne, ont, pch, pnw, win. |
ascending | boolean | — | Whether to sort in ascending order. Default is ascending. |
Parameters from the server's own tool schema.
This tool performs read-only queries on FIRST Robotics Competition data. It retrieves and filters team-event records with various parameters but performs no modifications, deletions, executions, or financial transactions. The tool is purely informational and has no side effects beyond returning data.
From the tool's definition Tool name is 'get_team_events' and description explicitly states 'List FIRST Robotics Competition (FRC) team-event records' with filtering and sorting capabilities. Verbs used are 'List', 'Filter', 'Sort', and 'paginate' — all read-only query operations.
Risk signalsHigh parameter count (12 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List FIRST Robotics Competition (FRC) team-event records with flexible filters. Each row represents one team's performance at one event (rank, record, EPA, awards). Filter any combination of team (one team across all events), year, event (all teams at one event - great for getting an event's full team list with stats), country, state, district, type (regional, district, district_cmp, champs_div, einstein, offseason), and week (0-8). Sort with metric/ascending and paginate with limit/offset. Use this to answer "show every event team 254 has attended in 2024", "list all teams at 2024flor with their ranks", or "rank teams by EPA across all 2024 district championships". It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_team_events accepts 12 parameters: team, type, week, year, event, limit, state, metric, offset, country, district, 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_team_events: 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_events 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_events 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_events. 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_events 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 →