sleeper_search_players
Search the Sleeper NFL player database by name (and optionally team/position). Returns slim records with injury status, depth-chart order, team and position. The full player set is cached for 24h.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/sleeper-search-players.md
What sleeper_search_players does on Sports Hub
AI agents call sleeper_search_players to retrieve information from Sports Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sleeper_search_players is rated Low
This tool retrieves publicly available sports data (player information, injury status, team assignments) from a cached database. It performs a search query and returns results without creating, modifying, deleting, or executing any operations. The cached 24-hour refresh cycle further confirms this is a passive data retrieval mechanism with no side effects.
From the tool's definition Tool description states 'Search the Sleeper NFL player database by name' and 'Returns slim records with injury status, depth-chart order, team and position.' The verb 'search' and 'returns' indicate a read-only query operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs sleeper_search_players safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sports Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sleeper_search_players, this is the rule to start with:
sleeper_search_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 Sports Hub, apply this rule, and every sleeper_search_players call is checked against it from then on.
Questions about sleeper_search_players
Search the Sleeper NFL player database by name (and optionally team/position). Returns slim records with injury status, depth-chart order, team and position. The full player set is cached for 24h. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.
Register the Sports Hub MCP server in PolicyLayer and add a rule for sleeper_search_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 Sports Hub. Nothing to install.
sleeper_search_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_search_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_search_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_search_players is provided by the Sports Hub MCP server (mcp-sports-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sports Hub, and thousands of servers like it.
This server
Across the catalogue