Get detailed information for a specific player.
AI agents call get_player_info to retrieve information from NHL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves player data from the NHL API. It performs a read-only lookup operation that does not modify, execute, delete, or commit any financial transactions. The blast radius of misuse is minimal—an agent could only retrieve information already publicly available through the NHL API.
From the tool's definition Tool name 'get_player_info' and description 'Get detailed information for a specific player' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get detailed information for a specific player. It is categorised as a Read tool in the NHL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NHL MCP Server MCP server in PolicyLayer and add a rule for get_player_info: 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 NHL MCP Server. Nothing to install.
get_player_info 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_info 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_info. 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_info is provided by the NHL MCP Server MCP server (sanchorelaxo/mcp-server-sandbox). 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 →