AI agents call get_steam_owned_games to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
steamid | string | Yes | Steam64 ID |
include_appinfo | boolean | — | Include game names (default true) |
include_played_free_games | boolean | — |
Parameters from the server's own tool schema.
This tool queries and retrieves publicly or semi-publicly available Steam user data (owned games list). It has no side effects, does not modify data, execute code, delete information, or move money. This is a straightforward data retrieval operation, which falls under the Read category. Severity is low because misuse would only expose user gaming preferences, not sensitive financial or security-critical information.
From the tool's definition Tool name and description: 'Get games owned by a Steam user' — uses the verb 'Get' and retrieves a list of games associated with a Steam account. No modification, deletion, or execution of external operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Get games owned by a Steam user. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_steam_owned_games accepts 4 parameters: api_key, steamid, include_appinfo, include_played_free_games. Required: steamid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for get_steam_owned_games: 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 UnClick. Nothing to install.
get_steam_owned_games 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_steam_owned_games 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_steam_owned_games. 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_steam_owned_games is provided by the UnClick MCP server (@unclick/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 →