AI agents call sleeper_league_matchups to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
week | number | Yes | |
league_id | string | Yes |
Parameters from the server's own tool schema.
This tool queries and returns fantasy league matchup data without creating, modifying, executing code, deleting data, or moving money. It is a straightforward read/retrieval operation with no destructive or risky side effects.
From the tool's definition Tool name 'sleeper_league_matchups' and description 'Get matchups for a Sleeper fantasy league week' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get matchups for a Sleeper fantasy league week. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sleeper_league_matchups accepts 2 parameters: week, league_id. Required: week, league_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sleeper_league_matchups: 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 UnClick. Nothing to install.
sleeper_league_matchups 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 sleeper_league_matchups 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 sleeper_league_matchups. 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.
sleeper_league_matchups is provided by the UnClick MCP server (@unclick/mcp-server). 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 →