Import a game from external services (Steam, GOG) into your Lutris library
AI agents use import_service_game to create or update resources in Lutris MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lutris MCP Server environment.
This tool creates or adds new game records to the Lutris library from external sources, which is a reversible modification operation. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not move money (would be Financial).
From the tool's definition Tool name 'import_service_game' and description 'Import a game from external services (Steam, GOG) into your Lutris library' indicate creation of new game entries in the Lutris database.
Attacks that exploit this kind of access
Import a game from external services (Steam, GOG) into your Lutris library. It is categorised as a Write tool in the Lutris MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lutris MCP Server MCP server in PolicyLayer and add a rule for import_service_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.
import_service_game is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_service_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 import_service_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.
import_service_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 →