Get a single team's contribution to a single FIRST Robotics Competition (FRC) match - the per-robot view of one match. Returns which alliance the team was on (red/blue), the team's EPA going into the match, the team's predicted score contribution by component, and post-match outcome flags. Useful...
AI agents call get_team_match 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 |
match | string | Yes | Match key, e.g. 2024flor_qm20 |
Parameters from the server's own tool schema.
This tool retrieves historical FIRST Robotics Competition match data for analysis purposes. It queries existing data without creating, modifying, or deleting anything. The tool's function is purely informational—gathering statistics about team performance in a specific match. There are no side effects, no code execution, no data modification, and no irreversible operations.
From the tool's definition Tool description states it 'Get[s] a single team's contribution' and 'Returns' match statistics, EPA, and outcome flags. All verbs indicate data retrieval with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get a single team's contribution to a single FIRST Robotics Competition (FRC) match - the per-robot view of one match. Returns which alliance the team was on (red/blue), the team's EPA going into the match, the team's predicted score contribution by component, and post-match outcome flags. Useful for scouting and post-match analysis: "how much did team 2056 contribute to alliance score in 2024onham_sf2m1?". Requires both team (integer, no prefix) and match (match key like "2024flor_qm20"). For listing many team-match rows, 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_team_match accepts 2 parameters: team, match. Required: team, match. 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_match: 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_match 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_match 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_match. 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_match 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 →