AI agents call riot_match_history to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | |
puuid | string | Yes | |
region | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
This tool fetches historical game match data for a League of Legends account identified by PUUID. It is purely a retrieval operation with no capability to modify, delete, or execute actions. The data returned is historical and non-sensitive player game statistics. No blast radius from misuse by an AI agent.
From the tool's definition Tool name contains 'match_history' and description states 'Get match history' — a query operation that retrieves data with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Get match history for a LoL/Riot account by PUUID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
riot_match_history accepts 4 parameters: count, puuid, region, api_key. Required: puuid. 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 riot_match_history: 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.
riot_match_history 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 riot_match_history 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 riot_match_history. 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.
riot_match_history 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →