Player stats. stat_type: season (default), career, game_log, hustle, defense, advanced. Accepts player name or ID.
AI agents call get_player_stats 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 and queries NBA player statistics based on various statistical categories and time periods. It has no side effects, does not modify data, and does not execute external operations beyond data lookup. It is purely informational and falls clearly into the Read category. Low severity due to minimal harm potential from misuse.
From the tool's definition Tool description states 'Player stats' with options for 'season', 'career', 'game_log', 'hustle', 'defense', 'advanced' and accepts 'player name or ID'. All described functions are queries that retrieve existing data without modification.
Documented attack patterns abuse exactly the kind of access get_player_stats 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_player_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_player_stats": {}
}
} get_player_stats 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.
Player stats. stat_type: season (default), career, game_log, hustle, defense, advanced. Accepts player name or ID. 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_player_stats: 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_player_stats 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_player_stats 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_player_stats. 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_player_stats 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.