AI agents call get_teams_by_year_simple 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 historical FRC (FIRST Robotics Competition) team roster data for a specified year. It performs no mutations, deletions, or external operations - it simply queries and returns a filtered dataset. The 'simple' variant indicates a lighter payload variant of a read operation. There is no capability to modify, delete, or execute actions.
From the tool's definition Tool description explicitly states 'Paginated list of FRC teams' - this is a query/retrieval operation that 'get[s]' team data with no modification capability. Terms like 'list' and 'get' combined with 'reduced team fields' confirm data retrieval only.
Attacks that exploit this kind of access
Paginated list of FRC teams that competed in a given year with reduced team fields (key, team_number, nickname, name, location). Lighter than get_teams_by_year. 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_by_year_simple: 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_by_year_simple 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_by_year_simple 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_by_year_simple. 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_by_year_simple 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 →