Retrieve Zebra MotionWorks robot-tracking telemetry for a match: per-timestep XY field positions for every robot on red and blue alliances, plus the timestamp series. Only available for events with Zebra tracking installed (typically FIRST Championship divisions and a subset of regionals/district...
AI agents call get_match_zebra 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 returns historical match telemetry data from a robotics competition tracking system. It performs a read-only data retrieval operation with no side effects. The data returned (position coordinates and timestamps) is informational and already published. Misuse poses minimal risk—an AI agent cannot cause harm by reading publicly available match tracking data.
From the tool's definition Tool retrieves telemetry data: 'Retrieve Zebra MotionWorks robot-tracking telemetry for a match: per-timestep XY field positions for every robot'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Retrieve Zebra MotionWorks robot-tracking telemetry for a match: per-timestep XY field positions for every robot on red and blue alliances, plus the timestamp series. Only available for events with Zebra tracking installed (typically FIRST Championship divisions and a subset of regionals/district championships). Useful for advanced scouting, defense analysis, and trajectory visualization. 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_match_zebra: 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_match_zebra 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_match_zebra 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_match_zebra. 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_match_zebra 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 →