Get standings information for each season.
AI agents call get_standings_season 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 historical or current NHL standings data. The verb 'get' and the passive operation of retrieving standings information with no side effects clearly indicate a Read category tool. There is no capability to modify, delete, execute code, or affect any system state. The low severity reflects that accessing public sports statistics poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_standings_season' and description 'Get standings information for each season' indicate a retrieval operation with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
Get standings information for each season. 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_standings_season: 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_standings_season 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_standings_season 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_standings_season. 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_standings_season 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 →