Get one team's performance at one specific FIRST Robotics Competition (FRC) event. Returns the team's qualification rank, qualification record (W-L-T), playoff alliance and result, EPA at this event (start, end, mean, breakdown by score component), and award list. Requires both team (integer, no ...
AI agents call get_team_event 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 |
event | string | Yes | Event key, e.g. 2024flor |
Parameters from the server's own tool schema.
This tool purely retrieves historical performance metrics and statistics about FIRST Robotics Competition events. It has no side effects, cannot modify data, and presents no blast radius if called by an AI agent. It is a straightforward query tool for fetching publicly available competition data.
From the tool's definition Tool description explicitly states it 'Get[s] one team's performance' and 'Returns the team's qualification rank, qualification record, playoff alliance and result, EPA at this event, and award list.' All operations are data retrieval with no modification,…
Attacks that exploit this kind of access
Get one team's performance at one specific FIRST Robotics Competition (FRC) event. Returns the team's qualification rank, qualification record (W-L-T), playoff alliance and result, EPA at this event (start, end, mean, breakdown by score component), and award list. Requires both team (integer, no prefix) and event (event key like "2024flor"). Use this to answer "how did team 2056 do at 2024onham?", "what was team 254's EPA at champs?", or "what awards did team 1114 win at their district championship?". For browsing many team-event combinations, use get_team_events. It is categorised as a Read tool in the Statbotics MCP Server, which means it retrieves data without modifying state.
get_team_event accepts 2 parameters: team, event. Required: team, event. 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_event: 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_event 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_event 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_event. 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_event 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 →