Resolve player name to player_id. Returns top matches with active/inactive status.
AI agents call resolve_player_id 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 only looks up and returns player ID information based on a name query. It retrieves data with no side effects, modifications, or destructive actions. Misuse potential is minimal as it only exposes player identification data.
From the tool's definition "Resolve player name to player_id. Returns top matches with active/inactive status."
Documented attack patterns abuse exactly the kind of access resolve_player_id 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 resolve_player_id:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_player_id": {}
}
} resolve_player_id 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.
Resolve player name to player_id. Returns top matches with active/inactive status. 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 resolve_player_id: 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.
resolve_player_id 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 resolve_player_id 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 resolve_player_id. 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.
resolve_player_id 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.