lichess_get_users_status
Get realtime online + streaming status for up to 100 Lichess users in a single call.
This record as markdown: /tools/io-github-lacausecrypto-sports-hub/lichess-get-users-status.md
What lichess_get_users_status does on Sports Hub
AI agents call lichess_get_users_status 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 lichess_get_users_status is rated Low
This is a simple data retrieval operation querying user status on Lichess. It has no side effects, makes no modifications, executes no code, and poses minimal risk. The blast radius of misuse is negligible; an attacker could only learn who is online or streaming, which is typically public information on such platforms.
From the tool's definition Tool retrieves 'realtime online + streaming status for up to 100 Lichess users' — a read-only query with no modification, deletion, or execution capability. Returns status information only.
Attacks that exploit this kind of access
The rule that runs lichess_get_users_status 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 lichess_get_users_status, this is the rule to start with:
lichess_get_users_status 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 lichess_get_users_status call is checked against it from then on.
Questions about lichess_get_users_status
Get realtime online + streaming status for up to 100 Lichess users in a single call. 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 lichess_get_users_status: 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.
lichess_get_users_status 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 lichess_get_users_status 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 lichess_get_users_status. 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.
lichess_get_users_status 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