AI agents call get_player_profile to retrieve information from Chess Com MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available player profile information from Chess.com with no side effects, no data modification, and no ability to execute code or perform financial transactions. The blast radius of misuse is minimal—an agent could at worst retrieve unwanted profile information, which is already public. This is a straightforward Read operation.
From the tool's definition Tool name 'get_player_profile' and description 'Get a player' indicate a retrieval operation. The server description confirms this provides 'access to Chess.com player data' through 'search and analyze' operations.
Documented attack patterns abuse exactly the kind of access get_player_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chess Com MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_player_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_player_profile": {}
}
}get_player_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a player. It is categorised as a Read tool in the Chess Com MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chess Com MCP Server MCP server in PolicyLayer and add a rule for get_player_profile: 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 Chess Com MCP Server. Nothing to install.
get_player_profile 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_player_profile 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_player_profile. 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_player_profile is provided by the Chess Com MCP Server MCP server (pab1it0/chess-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Chess Com MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Chess Com MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.