Fetch every match played at a specific FRC event, including qualification, playoff, and finals. Returns full match records with alliance compositions, final scores, game-specific score breakdown (auto/teleop/endgame components), winning alliance, video links, and timing (scheduled/predicted/actua...
AI agents call get_event_matches to retrieve information from Tba without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool for FIRST Robotics Championship event information. It queries and returns historical match records, scores, and metadata without performing any mutations, deletions, or executing external operations. The blast radius of misuse is minimal—an agent could only spam requests or extract public competition data.
From the tool's definition Tool fetches match data from FRC events including scores, alliances, and video links. The description uses 'Fetch' and 'Returns' indicating data retrieval with no side effects. No create, modify, delete, or execution capabilities mentioned.
Attacks that exploit this kind of access
Fetch every match played at a specific FRC event, including qualification, playoff, and finals. Returns full match records with alliance compositions, final scores, game-specific score breakdown (auto/teleop/endgame components), winning alliance, video links, and timing (scheduled/predicted/actual/post-result). Lighter variants: get_event_matches_simple, get_event_matches_keys. It is categorised as a Read tool in the Tba MCP Server, which means it retrieves data without modifying state.
Register the Tba MCP server in PolicyLayer and add a rule for get_event_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 Tba. Nothing to install.
get_event_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_event_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_event_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_event_matches is provided by the Tba MCP server (@withinfocus/tba-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 →