List FIRST Robotics Competition (FRC) events with optional filters - the discovery tool for finding event keys and browsing the season schedule. Returns an array of events with name, key, dates, location, week, type, EPA stats, and predictions. Filter by year (4-digit, >=2002), country, state, di...
AI agents call get_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 |
|---|---|---|---|
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) |
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 retrieves and queries FRC event data with optional filters but performs no side effects. It is purely informational—users can browse event schedules, filter by various criteria, and paginate results. There is no capability to create, modify, delete, or execute any operations. This clearly falls under the 'Read' category as a safe data retrieval tool.
From the tool's definition Tool description explicitly states it is a 'discovery tool for finding event keys and browsing the season schedule' that 'returns an array of events' with filtering and pagination capabilities.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
List FIRST Robotics Competition (FRC) events with optional filters - the discovery tool for finding event keys and browsing the season schedule. Returns an array of events with name, key, dates, location, week, type, EPA stats, and predictions. Filter by year (4-digit, >=2002), country, state, district, type (regional, district, district_cmp, champs_div, einstein, offseason), and week (0-8 of the season; 8 = championship). Sort with metric/ascending and paginate with limit/offset. Use this to answer "what regionals were in California in 2024?", "list all week 1 events this year", or "find the FRC championship divisions" (year=YEAR, type="champs_div"). If you need a single event you already know, use get_event. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_events accepts 10 parameters: type, week, year, 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_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_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_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_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_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 →