Fetch summoner info, league entries, and recent matches
AI agents call fetch_summoner_context 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 aggregates publicly available League of Legends player statistics and match history through the Riot Games API. It retrieves data without modifying, deleting, or executing any side effects. The 'Fetch' verb and the nature of Riot's public API endpoints confirm this is informational read access only. No financial transactions, code execution, or destructive operations are possible.
From the tool's definition Tool description states 'Fetch summoner info, league entries, and recent matches' — all retrieval operations with no modification capability.
Attacks that exploit this kind of access
Fetch summoner info, league entries, and recent matches. 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 fetch_summoner_context: 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.
fetch_summoner_context 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 fetch_summoner_context 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 fetch_summoner_context. 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.
fetch_summoner_context 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 →