wnba_get_player_shot_locations
Get WNBA player shot location statistics
This record as markdown: /tools/io-balldontlie-mcp/wnba-get-player-shot-locations.md
What wnba_get_player_shot_locations does on Mcp
AI agents call wnba_get_player_shot_locations to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wnba_get_player_shot_locations is rated Low
This tool retrieves historical shot location data for WNBA players from the sports API. It queries and returns existing statistics without creating, modifying, deleting, or executing any operations. The data retrieval has no side effects on the system or external state, making it a straightforward Read category tool with low risk.
From the tool's definition Tool name 'wnba_get_player_shot_locations' and description 'Get WNBA player shot location statistics' indicate a data retrieval operation with no side effects. The verb 'get' and the query nature of retrieving statistics confirm read-only behavior.
Attacks that exploit this kind of access
The rule that runs wnba_get_player_shot_locations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wnba_get_player_shot_locations, this is the rule to start with:
wnba_get_player_shot_locations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every wnba_get_player_shot_locations call is checked against it from then on.
Questions about wnba_get_player_shot_locations
Get WNBA player shot location statistics. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for wnba_get_player_shot_locations: 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 Mcp. Nothing to install.
wnba_get_player_shot_locations 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 wnba_get_player_shot_locations 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 wnba_get_player_shot_locations. 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.
wnba_get_player_shot_locations is provided by the MCP server (https://mcp.balldontlie.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue