AI agents call get_team_events_all 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 and queries historical FRC event data for a given team. It has no side effects, does not modify any data, and does not execute arbitrary code or trigger external operations. It is purely informational, making it a Read operation with low severity due to the public nature of FRC competition data.
From the tool's definition Tool description states 'List every FRC event a team has competed at' and 'Returns full event records'. The verb 'List' and 'Returns' indicate data retrieval with no modification or deletion capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every FRC event a team has competed at across all years it has participated. Returns full event records. Use to map 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_all: 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_all 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_all 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_all. 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_all 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 →