Get real-time users status
AI agents call get_users_status to retrieve information from Lichess Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | string | — | User IDs separated by commas. Up to 100 IDs. |
withSignal | boolean | — | Include network signal strength (1-4) |
withGameIds | boolean | — | Include IDs of ongoing games |
withGameMetas | boolean | — | Include metadata of ongoing games |
Parameters from the server's own tool schema.
This tool retrieves real-time status data about users on the Lichess platform without creating, modifying, executing, or deleting any data. It is a pure read operation with minimal security risk, as it only exposes publicly available or user-permitted status information typical of a social chess platform.
From the tool's definition Tool name 'get_users_status' and description 'Get real-time users status' indicate retrieval of user status information with no modification or execution of actions.
Attacks that exploit this kind of access
Get real-time users status. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_users_status accepts 4 parameters: ids, withSignal, withGameIds, withGameMetas. The full parameter table on this page comes from the server's own tool schema.
Register the Lichess Integration MCP server in PolicyLayer and add a rule for 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 Lichess Integration. Nothing to install.
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 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 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.
get_users_status is provided by the Lichess Integration MCP server (karayaman/lichess-mcp). 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 →