get_teams_by_year

List every FRC team that competed in a given season year, paginated in groups of 500. Returns full team profiles. Use to scope team enumeration to a single competition season. Lighter variants: get_teams_by_year_simple, get_teams_by_year_keys.

Server Tba @withinfocus/tba-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_teams_by_year does on Tba

AI agents call get_teams_by_year 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.

Why get_teams_by_year needs a policy

This tool retrieves and queries historical team data from The Blue Alliance (FRC competition database). It has no side effects—it does not create, modify, delete, or execute operations. The pagination and filtering by year are standard read-operation features. The availability of lighter variants (get_teams_by_year_simple, get_teams_by_year_keys) further confirms this is a read-only enumeration tool.

From the tool's definition Tool description states 'List every FRC team that competed in a given season year' and 'Returns full team profiles.' The verb 'List' combined with 'Returns' indicates data retrieval with no modification capabilities.

Questions about get_teams_by_year

What does the get_teams_by_year tool do? +

List every FRC team that competed in a given season year, paginated in groups of 500. Returns full team profiles. Use to scope team enumeration to a single competition season. Lighter variants: get_teams_by_year_simple, get_teams_by_year_keys. It is categorised as a Read tool in the Tba MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_teams_by_year? +

Register the Tba MCP server in PolicyLayer and add a rule for get_teams_by_year: 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.

What risk level is get_teams_by_year? +

get_teams_by_year is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_teams_by_year? +

Yes. Add a rate_limit block to the get_teams_by_year 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.

How do I block get_teams_by_year completely? +

Set action: deny in the PolicyLayer policy for get_teams_by_year. 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.

What MCP server provides get_teams_by_year? +

get_teams_by_year 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.

// THE FULL RECORD

get_teams_by_year 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.