List FIRST Robotics Competition (FRC) matches with optional filters. Returns an array of match records (alliances, scores, predictions, EPA-based win probabilities, elim flag). Filter by team (every match a team played in), year, event (every match at one event), week (0-8), and elim (true for pl...
AI agents call get_matches 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 |
|---|---|---|---|
elim | boolean | — | Whether the match is an elimination match. |
team | integer | — | Team number (no prefix), e.g. 86 |
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. |
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 is a data retrieval tool that queries a FRC robotics competition database. It performs read-only operations—filtering, sorting, and paginating match records—with no side effects. The low severity reflects that misuse would only expose public competition data without risk of data loss, financial impact, or system compromise.
From the tool's definition Tool description states "List FIRST Robotics Competition (FRC) matches" and "Returns an array of match records" with filtering and sorting capabilities.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List FIRST Robotics Competition (FRC) matches with optional filters. Returns an array of match records (alliances, scores, predictions, EPA-based win probabilities, elim flag). Filter by team (every match a team played in), year, event (every match at one event), week (0-8), and elim (true for playoff/elimination matches only, false for qualifications only). Sort with metric/ascending and paginate with limit/offset. Use this to answer "show all of team 254's matches in 2024", "list every elim match at 2024cmptx", or "find the highest-scoring matches of week 6". For per-team match contributions (a team's individual EPA in a match), use get_team_matches. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_matches accepts 9 parameters: elim, team, week, year, event, 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_matches: 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_matches 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_matches 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_matches. 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_matches 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 →