AI agents call get_district_teams_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 queries and retrieves public FRC (First Robotics Competition) district team data. The operation is read-only with no side effects, no data modification, no execution of arbitrary code, and no destructive capabilities. The description explicitly characterizes it as a lightweight enumeration (listing), confirming it is a data retrieval function.
From the tool's definition Tool name 'get_district_teams_keys' and description 'List team keys in an FRC district. Lightest enumeration of a district' indicate a retrieval operation that enumerates and returns team identifiers.
Attacks that exploit this kind of access
List team keys in an FRC district. Lightest enumeration of a district. 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_district_teams_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_district_teams_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_district_teams_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_district_teams_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_district_teams_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.
get_district_teams_keys is one line of Tba's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →