riot_match_history
Get match history for a LoL/Riot account by PUUID.
This record as markdown: /tools/creativelead-unclick/riot-match-history.md
What riot_match_history does on UnClick
AI agents call riot_match_history 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 |
|---|---|---|---|
count | number | — | |
puuid | string | — | |
region | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why riot_match_history is rated Low
This tool queries and retrieves historical match data from Riot's API for a League of Legends account identified by PUUID. It performs a read-only operation with no side effects, no code execution, no data modification, and no financial impact. The blast radius of misuse is minimal—an attacker could only access publicly available or user-owned match history data.
From the tool's definition Tool name 'riot_match_history' and description 'Get match history' indicate data retrieval with no modification or execution of external operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs riot_match_history 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 riot_match_history, this is the rule to start with:
riot_match_history 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 riot_match_history call is checked against it from then on.
Questions about riot_match_history
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. 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 (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