Get a player
AI agents call steam_getOwnedGames 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 retrieves information about games owned by a player. It performs a query/fetch operation with no side effects—it does not create, modify, delete, or execute any actions. The blast radius is minimal since it only returns existing data about a player's game library. Although the description is truncated and uninformative, the tool name strongly indicates a simple read operation.
From the tool's definition Tool name 'steam_getOwnedGames' and description 'Get a player' indicate querying/retrieving player data without modification. The tool name explicitly suggests a read operation (get) on owned games data.
Attacks that exploit this kind of access
Get a player. 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_getOwnedGames: 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_getOwnedGames 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_getOwnedGames 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_getOwnedGames. 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_getOwnedGames 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 →