Search games from external services (Steam, GOG, etc.) synced in Lutris
AI agents call search_service_games to retrieve information from Lutris 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 or queries game data from external services synced in Lutris without modifying, deleting, or executing arbitrary code. It is a straightforward read operation with minimal blast radius—worst case, an agent performs many searches, causing performance degradation rather than data loss or execution of code.
From the tool's definition Tool description states it 'Search games from external services' and the server description emphasizes 'browse, search' as core capabilities. The word 'search' indicates a query operation with no data modification.
Attacks that exploit this kind of access
Search games from external services (Steam, GOG, etc.) synced in Lutris. It is categorised as a Read tool in the Lutris MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lutris MCP Server MCP server in PolicyLayer and add a rule for search_service_games: 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 Lutris MCP Server. Nothing to install.
search_service_games 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 search_service_games 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 search_service_games. 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.
search_service_games is provided by the Lutris MCP Server MCP server (praeses0/lutris-mcp). 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 →