chesscom.player.stats
Get a Chess.com player's rating + record across all time controls (rapid, blitz, bullet, daily, daily960, tactics, lessons, puzzle_rush). Returns highest rating, current rating, win/loss/draw counts.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/chesscom.player.stats.md
What chesscom.player.stats does on Apibase
AI agents call chesscom.player.stats to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
username | string | Yes | Chess.com username (3–25 characters; lowercase letters, digits, hyphens, and underscores only). Example: "hikaru", "magnuscarlsen". |
Parameters from the server's own tool schema.
Why chesscom.player.stats is rated Low
Tool retrieves public player statistics from Chess.com without modifying data or executing external operations.
From the tool's definition Get a Chess.com player's rating + record; returns highest rating, current rating, win/loss/draw counts.
Attacks that exploit this kind of access
The rule that runs chesscom.player.stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chesscom.player.stats, this is the rule to start with:
chesscom.player.stats 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 Apibase, apply this rule, and every chesscom.player.stats call is checked against it from then on.
Questions about chesscom.player.stats
Get a Chess.com player's rating + record across all time controls (rapid, blitz, bullet, daily, daily960, tactics, lessons, puzzle_rush). Returns highest rating, current rating, win/loss/draw counts. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
chesscom.player.stats accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for chesscom.player.stats: 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 Apibase. Nothing to install.
chesscom.player.stats 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 chesscom.player.stats 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 chesscom.player.stats. 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.
chesscom.player.stats is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue