AI agents call sleeper_players 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 |
|---|---|---|---|
sport | string | — |
Parameters from the server's own tool schema.
This tool queries and retrieves data about NFL players from the Sleeper service. It has no side effects, does not modify or delete data, and does not execute arbitrary code or trigger external operations. It is a straightforward data retrieval endpoint.
From the tool's definition Tool description states 'Get all NFL players from Sleeper' — a retrieval operation with no modification, deletion, or execution of external operations. The verb 'get' is characteristic of Read operations.
Attacks that exploit this kind of access
Get all NFL players from Sleeper. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sleeper_players accepts 1 parameter: sport. 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_players: 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_players 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_players 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_players. 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_players 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 →