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 queries and retrieves game information from the Steam Web API. The described functionality (fetching description, genres, tags, release date, Metacritic score, and price) are all informational reads with no capability to modify, delete, or execute operations. It has minimal blast radius if misused by an AI agent, as it only returns read-only game store data.
From the tool's definition Tool retrieves 'store details for a game — description, genres, tags, release date, Metacritic score, and price.' These are read-only queries of publicly available game metadata with no side effects or data modification.
Attacks that exploit this kind of access
Get store details for a game — description, genres, tags, release date, Metacritic score, and price. Accepts game name or appid. 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 (jkiley129/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 →