This record as markdown: /tools/creativelead-unclick/coc-player.md
What coc_player does on UnClick
AI agents call coc_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 |
|---|---|---|---|
api_key | string | — | |
playerTag | string | — |
Parameters from the server's own tool schema.
Why coc_player is rated Low
This tool retrieves game player information based on an identifier (tag). It performs a read-only query operation with no side effects, data modification, code execution, or destructive capabilities. The blast radius of misuse is minimal — an attacker could enumerate player information but cannot modify game state, execute code, or cause financial harm.
From the tool's definition Tool name is 'coc_player' and description states 'Get a Clash of Clans player by tag' — purely retrieves player data from the game with no modification capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs coc_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 coc_player, this is the rule to start with:
coc_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 coc_player call is checked against it from then on.
Questions about coc_player
Get a Clash of Clans player by tag. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
coc_player accepts 2 parameters: api_key, playerTag. 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 coc_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.
coc_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 coc_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 coc_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.
coc_player 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