Get detailed information about a Steam game including description, price, and requirements
AI agents call get_game_details to retrieve information from Steam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation against the Steam Web API to fetch publicly available game metadata (description, price, system requirements). It has no ability to modify, delete, or execute operations. The data retrieved is read-only reference information that does not affect game state, user accounts, or any external systems.
From the tool's definition Tool retrieves 'detailed information about a Steam game including description, price, and requirements' with no modification or side effects. The description uses 'Get' and specifies data retrieval operations typical of Read category.
Attacks that exploit this kind of access
Get detailed information about a Steam game including description, price, and requirements. It is categorised as a Read tool in the Steam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Steam MCP Server 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 MCP Server. 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 MCP server (sharkusmanch/steam-mcp-server). 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 →