Get a message thread
AI agents call get_thread 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 |
|---|---|---|---|
userId | string | — | User ID of the other person |
Parameters from the server's own tool schema.
This tool retrieves message thread data from the Lichess platform. It has no side effects, does not modify or delete data, and does not trigger external operations or financial transactions. It is a simple data retrieval operation, fitting the Read category. Severity is low because exposing message threads carries minimal risk—they are user-accessible data on the platform.
From the tool's definition Tool name 'get_thread' and description 'Get a message thread' indicate retrieval of existing data without modification. The verb 'Get' is a standard read operation.
Attacks that exploit this kind of access
Get a message thread. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
get_thread accepts 1 parameter: userId. 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_thread: 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_thread 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_thread 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_thread. 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_thread 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 →