This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cr-player.md
What cr_player does on UnClick
AI agents call cr_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 | Yes |
Parameters from the server's own tool schema.
Why cr_player is rated Low
This is a straightforward data retrieval operation that fetches player information from a Clash Royale game service. It has no side effects, does not modify data, and presents minimal risk if misused by an AI agent. The only concern would be privacy (exposing player stats), which is mitigated by the public nature of Clash Royale player data.
From the tool's definition Tool name and description: 'Get a Clash Royale player by tag' — a retrieval operation that queries game data for a specific player profile based on a tag identifier. No modification, deletion, or execution of commands.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs cr_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 cr_player, this is the rule to start with:
cr_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 cr_player call is checked against it from then on.
Questions about cr_player
Get a Clash Royale player by tag. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cr_player accepts 2 parameters: api_key, playerTag. Required: 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 cr_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.
cr_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 cr_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 cr_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.
cr_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