This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/chess-player.md
What chess_player does on UnClick
AI agents call chess_player 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 | Yes |
Parameters from the server's own tool schema.
Why chess_player is rated Low
This tool retrieves publicly available chess player information from Chess.com. It performs a simple data lookup with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal — an AI agent could at worst retrieve player profiles at scale, which poses negligible risk. No side effects, no data modification, no destructive or financial impact.
From the tool's definition Tool description states 'Get a Chess.com player profile' — a retrieval operation with no modification or side effects. The verb 'Get' and the nature of fetching public profile data indicates a read-only query.
Attacks that exploit this kind of access
The rule that runs chess_player 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, this is the rule to start with:
chess_player 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 call is checked against it from then on.
Questions about chess_player
Get a Chess.com player profile. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
chess_player accepts 1 parameter: username. Required: 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: 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 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 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. 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 is provided by the UnClick MCP server (@unclick/mcp-server). 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