sleeper_get_user

Get a Sleeper user (profile, user_id, display name) by username or numeric user id.

SERVERSports Hub SOURCEmcp-sports-hub

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/io-github-lacausecrypto-sports-hub/sleeper-get-user.md

WHAT IT DOES

What sleeper_get_user does on Sports Hub

AI agents call sleeper_get_user 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.

RISK

Why sleeper_get_user is rated Low

This tool queries and retrieves publicly available user profile data from Sleeper (a fantasy sports platform). The use of 'Get' and the parameters (username or user_id lookup) confirm read-only retrieval. There are no side effects, data modifications, deletions, code execution, or financial transactions. The blast radius of misuse is minimal—an attacker could enumerate user profiles but cannot modify or delete data.

From the tool's definition Tool name 'sleeper_get_user' and description 'Get a Sleeper user (profile, user_id, display name) by username or numeric user id' indicate retrieval of user profile information with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sleeper_get_user 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_get_user, this is the rule to start with:

sleeper_get_user Allowed

sleeper_get_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sleeper_get_user": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sports Hub, apply this rule, and every sleeper_get_user call is checked against it from then on.

FAQ

Questions about sleeper_get_user

What does the sleeper_get_user tool do? +

Get a Sleeper user (profile, user_id, display name) by username or numeric user id. It is categorised as a Read tool in the Sports Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sleeper_get_user? +

Register the Sports Hub MCP server in PolicyLayer and add a rule for sleeper_get_user: 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.

What risk level is sleeper_get_user? +

sleeper_get_user is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sleeper_get_user? +

Yes. Add a rate_limit block to the sleeper_get_user 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.

How do I block sleeper_get_user completely? +

Set action: deny in the PolicyLayer policy for sleeper_get_user. 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.

What MCP server provides sleeper_get_user? +

sleeper_get_user 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.

KEEP EXPLORING

More on Sports Hub, and thousands of servers like it.

This server

All 396 Sports Hub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →