install_game · Lutris MCP Server MCP: Risk & Policy

WHAT IT DOES

What install_game does on Lutris MCP Server

AI agents invoke install_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.

WHY IT NEEDS A POLICY

Why install_game needs a policy

Installing a game executes external code (installer slugs or local setup executables) on the user's system. This is an Execute-category action because it triggers external operations whose effects depend on arguments. The blast radius is high as it can run arbitrary installation scripts, modify the filesystem, and potentially execute untrusted code from installer slugs.

From the tool's definition 'Install a game via Lutris (from installer slug or local setup executable)' — triggers an external installation operation that runs scripts/executables on the system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_game Rate-limited

install_game stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_game": {
      "limits": [
        {
          "counter": "install_game_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lutris MCP Server, so you can run agents against it safely.

FAQ

Questions about install_game

What does the install_game tool do? +

Install a game via Lutris (from installer slug or local setup executable). 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.

How do I enforce a policy on install_game? +

Register the Lutris MCP Server MCP server in PolicyLayer and add a rule for install_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.

What risk level is install_game? +

install_game is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_game? +

Yes. Add a rate_limit block to the install_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.

How do I block install_game completely? +

Set action: deny in the PolicyLayer policy for install_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.

What MCP server provides install_game? +

install_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.