get_steam_player_summaries
Get Steam player profile summaries for one or more Steam IDs.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/get-steam-player-summaries.md
What get_steam_player_summaries does on UnClick
AI agents call get_steam_player_summaries to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | Steam Web API key (or set STEAM_API_KEY) |
steamids | string | Yes | Comma-separated Steam64 IDs (up to 100) |
Parameters from the server's own tool schema.
Why get_steam_player_summaries is rated Low
This tool retrieves Steam player profile information, which is a read-only operation that queries public data. It does not create, modify, delete, execute code, or involve financial transactions. The blast radius of misuse is minimal—an agent could retrieve unwanted profile summaries, but this causes no harm to systems or data integrity.
From the tool's definition Tool name 'get_steam_player_summaries' and description 'Get Steam player profile summaries for one or more Steam IDs' indicate retrieval of publicly available profile data with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs get_steam_player_summaries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_steam_player_summaries, this is the rule to start with:
get_steam_player_summaries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every get_steam_player_summaries call is checked against it from then on.
Questions about get_steam_player_summaries
Get Steam player profile summaries for one or more Steam IDs. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_steam_player_summaries accepts 2 parameters: api_key, steamids. Required: steamids. 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_player_summaries: 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_player_summaries 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_player_summaries 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_player_summaries. 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_player_summaries 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue