Fetch user reviews for a Steam app with filters for language, sentiment, purchase type, and pagination. No API key required.
AI agents call steam_getReviews 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 queries publicly available Steam review data with no side effects. It retrieves existing reviews without creating, modifying, deleting, or executing code. The filtering and pagination parameters are used for data retrieval only. This is a straightforward Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description explicitly indicate it 'Fetch[es] user reviews' — a retrieval operation with 'filters for language, sentiment, purchase type, and pagination.' No mutation, deletion, or execution capability is mentioned.
Attacks that exploit this kind of access
Fetch user reviews for a Steam app with filters for language, sentiment, purchase type, and pagination. No API key required. 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 steam_getReviews: 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.
steam_getReviews 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 steam_getReviews 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 steam_getReviews. 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.
steam_getReviews is provided by the Steam MCP Server MCP server (tmhsdigital/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 →