AI agents call get_schedule 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 historical and upcoming game schedules and results from a public sports statistics database. It performs a read-only query with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is negligible—an agent could retrieve large amounts of publicly available sports data but cannot harm systems or cause financial impact.
From the tool's definition Tool name is 'get_schedule' and description states 'Games and results, chronological' — purely retrieval of existing data with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Games and results, chronological. For a tournament id, that series. 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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 →