AI agents call nba_search_players to retrieve information from Nba without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves player information from a public NBA stats database without any side effects. It is purely a query/search operation that returns data, fitting the Read category. The blast radius of misuse is minimal—worst case, an agent makes many redundant queries or searches for irrelevant players, with no impact on data integrity or system security.
From the tool's definition Tool description states 'Search NBA players by name' and server description emphasizes 'read-only tools to query live scores, box scores, player info'. No modification, deletion, execution, or financial capability is indicated.
Attacks that exploit this kind of access
Search NBA players by name using stats.nba.com playerindex. Defaults to the supplied season and active players only. It is categorised as a Read tool in the Nba MCP Server, which means it retrieves data without modifying state.
Register the Nba MCP server in PolicyLayer and add a rule for nba_search_players: 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 Nba. Nothing to install.
nba_search_players 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 nba_search_players 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 nba_search_players. 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.
nba_search_players is provided by the Nba MCP server (ufo2243/nba-mcp). 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 →