Fetch summoner info by name
AI agents call get_summoner 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 public game profile information by player name. It performs a simple lookup query against the Riot Games API and returns data without modifying, deleting, or executing arbitrary code. This is a straightforward Read operation. Severity is low because the data returned is typically public player information with minimal harm potential from misuse.
From the tool's definition Tool name 'get_summoner' and description 'Fetch summoner info by name' indicate retrieval of player data. The verb 'fetch' and context of querying 'summoner info' (public League of Legends player statistics) represent read-only operations with no data…
Attacks that exploit this kind of access
Fetch summoner info by name. 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_summoner: 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_summoner 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_summoner 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_summoner. 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_summoner 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 →