AI agents call get_game_details to retrieve information from Steam without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available information about Steam games without any side effects. It queries game metadata from the Steam Web API and returns informational data. There is no capability to modify, delete, execute code, or commit financial transactions. It is a straightforward data retrieval operation, placing it firmly in the Read category with low severity.
From the tool's definition Tool name is 'get_game_details' and description states it 'Get detailed info about a Steam game: price, description, genres, Metacritic score, platforms, release date, and more.' The verb 'Get' and the list of read-only attributes (price, description, genres,…
Attacks that exploit this kind of access
Get detailed info about a Steam game: price, description, genres, Metacritic score, platforms, release date, and more. It is categorised as a Read tool in the Steam MCP Server, which means it retrieves data without modifying state.
Register the Steam MCP server in PolicyLayer and add a rule for get_game_details: 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 Steam. Nothing to install.
get_game_details 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_game_details 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_game_details. 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_game_details is provided by the Steam MCP server (matheusslg/steam-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 →