Fetch match details by match ID
AI agents call get_match_details to retrieve information from LolByte 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 historical match information from the Riot Games API based on a match identifier. It performs no writes, deletes, code execution, or financial operations. The blast radius of misuse is minimal—an agent could only retrieve publicly available game statistics. Severity is low because League of Legends match data is not sensitive personal information and is designed to be publicly queryable.
From the tool's definition Tool name 'get_match_details' and description 'Fetch match details by match ID' indicate a data retrieval operation with no modification or deletion capability. The verb 'Fetch' is characteristic of Read operations.
Attacks that exploit this kind of access
Fetch match details by match ID. It is categorised as a Read tool in the LolByte MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LolByte MCP Server MCP server in PolicyLayer and add a rule for get_match_details: 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 LolByte MCP Server. Nothing to install.
get_match_details 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_details 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_details. 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_details is provided by the LolByte MCP Server MCP server (lolbyte-code/lolbyte-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 →