Launch an installed game via Lutris
AI agents invoke launch_game to trigger actions in Lutris MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Launching a game via Lutris triggers external code execution outside the MCP server's direct control. The effects are dependent on which game is selected and could include running arbitrary code packaged within game binaries, accessing system resources, and performing actions determined by game logic.
From the tool's definition Tool name 'launch_game' and description 'Launch an installed game via Lutris' indicate execution of an external operation (game process) whose effects depend on arguments (which game to launch).
Attacks that exploit this kind of access
Launch an installed game via Lutris. It is categorised as a Execute tool in the Lutris MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lutris MCP Server MCP server in PolicyLayer and add a rule for launch_game: 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.
launch_game is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the launch_game 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 launch_game. 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.
launch_game 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 →