AI agents call get_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 retrieves and queries team key data with no side effects. It returns read-only information (team keys as strings) in paginated form. There is no capability to modify, delete, or execute operations. This clearly falls under the Read category with low severity since team keys are likely public information in the FRC (FIRST Robotics Competition) context and exposure causes no harmful impact.
From the tool's definition Tool name 'get_teams_keys' and description 'Paginated listing of every registered FRC team key' indicates a retrieval operation that returns only identifiers without modification or deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Paginated listing of every registered FRC team key only (strings like. 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_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_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_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_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_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.
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 →