AI agents call get_district_events_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 lists event identifiers (keys) from an FRC district database. It performs a read-only query operation with no ability to modify, delete, or execute external actions. The description explicitly characterizes it as a 'lightweight enumeration,' confirming it is a simple data retrieval function. The blast radius of misuse is minimal—an attacker could only obtain public FRC event metadata.
From the tool's definition Tool name 'get_district_events_keys' and description 'List event keys' and 'enumeration of district events' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List event keys in an FRC district. Lightest enumeration of district events; ideal for driving per-event lookups across a district season. 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_district_events_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_district_events_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_district_events_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_district_events_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_district_events_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 →