AI agents call sports.nhl-standings to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns publicly available sports data without modifying, executing code, deleting, or moving money. It is a pure read operation. The 'pay-per-call' nature of the 2s.io service does not change the classification—the underlying operation is data retrieval. Severity is low because misuse would only retrieve sports standings data harmlessly.
From the tool's definition Tool retrieves 'Current NHL standings' with team statistics (conference, division, games played, wins, losses, OT losses, points, goal differential, and current streak) from the official NHL API. This is a query operation with no side effects.
Attacks that exploit this kind of access
Current NHL standings (official NHL api-web, free/keyless). Each team: conference, division, games played, wins, losses, OT losses, points, goal differential, and current streak. 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 sports.nhl-standings: 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.
sports.nhl-standings 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 sports.nhl-standings 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 sports.nhl-standings. 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.
sports.nhl-standings is provided by the MCP server (@2sio/mcp). 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 →