List available Lutris runners or Wine versions
AI agents call list_runners 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.
The tool retrieves and displays information about available runners/Wine versions. This is a query operation that reads data without creating, modifying, deleting, or executing any actions. It has minimal blast radius if misused by an AI agent, as it only provides informational output.
From the tool's definition Tool name 'list_runners' and description 'List available Lutris runners or Wine versions' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List available Lutris runners or Wine versions. 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 list_runners: 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.
list_runners 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 list_runners 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 list_runners. 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.
list_runners 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 →