AI agents call get_team_matches_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 match data for a sports team (FIRST Robotics, based on The Blue Alliance context). It performs a read-only query with no side effects, no code execution, no data modification, and no financial implications. The reduced field set confirms it is a simple data retrieval endpoint.
From the tool's definition Tool name uses 'get_' prefix and description states 'List every match a team played' — a retrieval operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every match a team played in a season year with reduced match fields (no game-specific score breakdown or videos). Lighter than get_team_matches. 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_matches_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_team_matches_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_team_matches_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_team_matches_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_team_matches_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 →