Test multiple OAuth tokens
AI agents call test_tokens 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 |
|---|---|---|---|
tokens | string | — | OAuth tokens separated by commas. Up to 1000. |
Parameters from the server's own tool schema.
Testing OAuth tokens is a read operation that queries the validity or status of tokens. However, it has medium severity because it involves OAuth tokens which are sensitive authentication credentials - misuse could expose information about valid tokens or authentication state. The description is minimal, so confidence is slightly reduced.
From the tool's definition 'Test multiple OAuth tokens' - testing/validating tokens is a read/query operation that checks token validity without modifying data
Attacks that exploit this kind of access
Test multiple OAuth tokens. It is categorised as a Read tool in the Lichess Integration MCP Server, which means it retrieves data without modifying state.
test_tokens accepts 1 parameter: tokens. 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 test_tokens: 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.
test_tokens 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 test_tokens 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 test_tokens. 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.
test_tokens 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 →