Get game story information for a specific game.
AI agents call get_game_story 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 retrieves game story data from the NHL API—a read-only operation that queries existing information. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal; an AI agent cannot cause harm by repeatedly fetching game stories. The tool fits the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool name 'get_game_story' and description 'Get game story information for a specific game' indicate a retrieval operation. The verb 'Get' combined with 'information for a specific game' describes querying/fetching data without modification or side effects.
Attacks that exploit this kind of access
Get game story information for a specific game. 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_game_story: 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_game_story 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_game_story 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_game_story. 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_game_story 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 →