AI agents call get_team_events_keys 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 tool retrieves publicly available FRC (FIRST Robotics Competition) event registration data for a team in a given season. It performs no mutations, executions, or destructive operations. The data returned (event keys) is informational and used to scope subsequent queries. This is a straightforward Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'List the event keys a team registered for' — a retrieval operation with no modification or side effects. The phrase 'Lightest variant' and 'useful for driving per-event queries' further confirms it is a query/lookup function.
Attacks that exploit this kind of access
List the event keys a team registered for in a given FRC season year. Lightest variant of get_team_events; useful for driving per-event queries scoped to a team. 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_team_events_keys: 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_team_events_keys 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_events_keys 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_events_keys. 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_events_keys 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 →