Get chronological death events for a player in a match with compact coaching context
AI agents call lol_get_player_deaths to retrieve information from League of Legends MCP 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 existing match data (death events) for analysis purposes. It performs no modifications, deletions, or external operations. The data is already recorded in the match history. The 'coaching context' descriptor suggests the tool formats retrieved data for educational review, not that it modifies anything.
From the tool's definition Tool name 'lol_get_player_deaths' and description 'Get chronological death events for a player in a match' indicate data retrieval.
Attacks that exploit this kind of access
Get chronological death events for a player in a match with compact coaching context. It is categorised as a Read tool in the League of Legends MCP Server MCP Server, which means it retrieves data without modifying state.
Register the League of Legends MCP Server MCP server in PolicyLayer and add a rule for lol_get_player_deaths: 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 League of Legends MCP Server. Nothing to install.
lol_get_player_deaths 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 lol_get_player_deaths 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 lol_get_player_deaths. 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.
lol_get_player_deaths is provided by the League of Legends MCP Server MCP server (rexlmanu/lol-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 →