🕹️ Get the player's recent match history.
AI agents call get_recent_matches_tool to retrieve information from MCP Riot Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries player match history data from the Riot Games API. It has no side effects, does not modify data, execute code, delete information, or involve financial transactions. It is purely informational retrieval, placing it in the Read category with low severity.
From the tool's definition Tool name 'get_recent_matches_tool' and description 'Get the player's recent match history' indicate data retrieval with no modification. The verb 'Get' and context of retrieving historical match data confirm this is a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_recent_matches_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Riot Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recent_matches_tool:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_matches_tool": {}
}
}get_recent_matches_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
🕹️ Get the player's recent match history. It is categorised as a Read tool in the MCP Riot Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Riot Server MCP server in PolicyLayer and add a rule for get_recent_matches_tool: 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 MCP Riot Server. Nothing to install.
get_recent_matches_tool 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 get_recent_matches_tool 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 get_recent_matches_tool. 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.
get_recent_matches_tool is provided by the MCP Riot Server MCP server (jifrozen0110/mcp-riot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Riot Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 MCP Riot Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.