AI agents call nba_live_play_by_play 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 performs a data retrieval operation against NBA.com's CDN. It queries and returns play-by-play game information based on a game ID parameter. There are no side effects, no data modification, no destructive operations, and no financial implications. The blast radius of misuse is minimal—an agent could only retrieve publicly available sports data. This is a straightforward Read operation.
From the tool's definition Tool description states 'Get live play-by-play actions' and server description emphasizes 'read-only tools to query live scores, box scores, player info, standings, and more'. The tool retrieves game data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get live play-by-play actions for a 10-digit NBA game id from cdn.nba.com. 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_live_play_by_play: 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_live_play_by_play 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_live_play_by_play 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_live_play_by_play. 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_live_play_by_play 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 →