📊 Get a detailed summary of a specific match for a given player.
AI agents call get_match_summary 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 historical match data from the Riot Games API without creating, modifying, deleting, or executing any operations. It poses minimal security risk as it only queries and returns information about past League of Legends matches for a specified player.
From the tool's definition Tool name 'get_match_summary' and description 'Get a detailed summary of a specific match' indicate retrieval of match data with no modifications. The word 'Get' and context of retrieving 'a detailed summary' confirm read-only data access.
Documented attack patterns abuse exactly the kind of access get_match_summary 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_match_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_match_summary": {}
}
}get_match_summary 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 a detailed summary of a specific match for a given player. 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_match_summary: 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_match_summary 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_match_summary 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_match_summary. 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_match_summary 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.