riot_match_history

Get match history for a LoL/Riot account by PUUID.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/riot-match-history.md

WHAT IT DOES

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
`count`	number	—
`puuid`	string	Yes
`region`	string	—
`api_key`	string	—

Parameters from the server's own tool schema.

RISK

Why riot_match_history is rated Low

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

RECOMMENDED RULE

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 Allowed

riot_match_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "riot_match_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about riot_match_history

What does the riot_match_history tool do? +

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.

What parameters does riot_match_history accept? +

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.

How do I enforce a policy on riot_match_history? +

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.

What risk level is riot_match_history? +

riot_match_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit riot_match_history? +

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.

How do I block riot_match_history completely? +

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.

What MCP server provides riot_match_history? +

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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

match_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →