Write or update a game
AI agents use write_game_config 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 modifies game details in the Lutris SQLite database. The 'write' and 'update' language indicates reversible changes to game configuration, not deletion or destruction. However, it operates on a gaming library system where modifications could affect user configurations and game launch behavior, warranting medium severity.
From the tool's definition Tool name is 'write_game_config' and description states 'Write or update a game', indicating it creates or modifies game configuration data reversibly.
Attacks that exploit this kind of access
Write or update a game. 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 write_game_config: 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.
write_game_config 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 write_game_config 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 write_game_config. 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.
write_game_config 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 →