Fetch recent match IDs by PUUID
AI agents call get_tft_recent_matches 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 identifiers for a player in Teamfight Tactics (TFT), a read-only query against the Riot Games API. There are no destructive, executable, financial, or modifying effects—it simply returns data already present in the system. Misuse would be limited to information gathering about game history, which poses minimal risk even if an AI agent operates it without constraint.
From the tool's definition Tool description states 'Fetch recent match IDs by PUUID' - a read-only retrieval operation that queries game data without modification or side effects. The name 'get_' prefix and 'fetch' verb confirm data retrieval semantics.
Attacks that exploit this kind of access
Fetch recent match IDs by PUUID. 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_tft_recent_matches: 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_tft_recent_matches 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_tft_recent_matches 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_tft_recent_matches. 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_tft_recent_matches 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 →