Export the Lutris library as JSON (games, categories, associations). Supports filtering by category, runner, and installed status, and optionally includes each game
AI agents call export_library 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 only reads and exports data from the Lutris SQLite database in JSON format. It supports filtering but has no side effects — it does not modify, delete, or create any data. Severity is low as misuse only exposes gaming library information.
From the tool's definition Export the Lutris library as JSON (games, categories, associations). Supports filtering by category, runner, and installed status
Attacks that exploit this kind of access
Export the Lutris library as JSON (games, categories, associations). Supports filtering by category, runner, and installed status, and optionally includes each game. 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 export_library: 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.
export_library 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 export_library 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 export_library. 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.
export_library 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 →