Play-by-play data for a game.
AI agents call get_play_by_play to retrieve information from Nba Stats without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves game statistics without modifying, executing, or deleting any data. It falls squarely within the Read category as it queries and returns historical NBA game information. The low severity reflects minimal risk if misused by an AI agent—retrieving public sports statistics poses no security, privacy, or operational threat.
From the tool's definition Tool name 'get_play_by_play' and description 'Play-by-play data for a game' indicate data retrieval. The verb 'get' and the context of retrieving historical game statistics confirm this is a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_play_by_play gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nba Stats, and nothing reaches the server without passing your rules. This is the rule we recommend for get_play_by_play:
{
"version": "1",
"default": "deny",
"tools": {
"get_play_by_play": {}
}
}get_play_by_play is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Play-by-play data for a game. It is categorised as a Read tool in the Nba Stats MCP Server, which means it retrieves data without modifying state.
Register the Nba Stats MCP server in PolicyLayer and add a rule for get_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 Stats. Nothing to install.
get_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 get_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 get_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.
get_play_by_play is provided by the Nba Stats MCP server (labeveryday/nba-stats-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nba Stats, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Nba Stats tools catalogued and risk-classified — across an index of 43,000+ MCP servers.