This record as markdown: /tools/creativelead-unclick/sleeper-trending-players.md
What sleeper_trending_players does on UnClick
AI agents call sleeper_trending_players to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | add or drop |
limit | number | — | |
sport | string | — | |
lookback_hours | number | — |
Parameters from the server's own tool schema.
Why sleeper_trending_players is rated Low
This tool retrieves information about trending players on the Sleeper platform (a fantasy sports platform). The verb 'Get' and the absence of any modification, deletion, or execution language clearly indicate this is a Read operation. There are no financial transactions, code execution, or data destruction involved.
From the tool's definition Tool name 'sleeper_trending_players' and description 'Get trending players on Sleeper' indicate a read-only query operation that retrieves trending player data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs sleeper_trending_players safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sleeper_trending_players, this is the rule to start with:
sleeper_trending_players is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every sleeper_trending_players call is checked against it from then on.
Questions about sleeper_trending_players
Get trending players on Sleeper. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sleeper_trending_players accepts 4 parameters: type, limit, sport, lookback_hours. 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_trending_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_trending_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_trending_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_trending_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_trending_players is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue