AI agents call get_standings to retrieve information from Swehockey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries ice-hockey standings information without side effects. It is a simple data lookup operation consistent with other sibling tools (get_schedule, get_teams, get_player_stats) that all perform read-only operations on the swehockey stats database. There is no capacity to modify, delete, or execute operations.
From the tool's definition Tool name 'get_standings' and description indicate retrieval of standings data from a sports statistics database. No modification, deletion, or execution capabilities are present. Returns tabular data for display purposes only.
Attacks that exploit this kind of access
Standings: for a tournament id, that table; for a league key, each of its. It is categorised as a Read tool in the Swehockey MCP Server, which means it retrieves data without modifying state.
Register the Swehockey MCP server in PolicyLayer and add a rule for get_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 Swehockey. Nothing to install.
get_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 get_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 get_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.
get_standings is provided by the Swehockey MCP server (troelskn/swehockey). 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 →