Get aggregate statistics about the Lutris game library
AI agents call get_library_stats 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 queries and returns aggregate data (statistics) from the Lutris library without creating, modifying, deleting, or executing any operations. It is purely informational and read-only. The low severity reflects minimal blast radius — an AI agent misusing this tool would only retrieve existing statistics, causing no harm.
From the tool's definition Tool name is 'get_library_stats' and description states it 'Get aggregate statistics about the Lutris game library' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get aggregate statistics about the Lutris game library. 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 get_library_stats: 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.
get_library_stats 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 get_library_stats 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 get_library_stats. 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.
get_library_stats 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 →