This record as markdown: /tools/creativelead-unclick/chess-player-stats.md
What chess_player_stats does on UnClick
AI agents call chess_player_stats to retrieve information from UnClick 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 | — |
Parameters from the server's own tool schema.
Why chess_player_stats is rated Low
This tool queries publicly available chess player statistics from Chess.com. It retrieves data without side effects, making it a Read operation. The severity is low as misuse would only expose already-public player statistics, with minimal blast radius.
From the tool's definition Tool description states 'Get Chess.com player statistics' - a retrieval operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
The rule that runs chess_player_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chess_player_stats, this is the rule to start with:
chess_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 UnClick, apply this rule, and every chess_player_stats call is checked against it from then on.
Questions about chess_player_stats
Get Chess.com player statistics. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
chess_player_stats accepts 1 parameter: username. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for chess_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 UnClick. Nothing to install.
chess_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 chess_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 chess_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.
chess_player_stats is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue