Get Steam player profile information including name, avatar, status, and current game
AI agents call get_player_summary 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 player profile metadata (name, avatar, status, current game) from the Steam Web API. It performs no writes, deletions, code execution, or financial operations. The data returned is typically publicly visible on Steam profiles. Misuse by an AI agent would at worst enable profiling or reconnaissance, which poses minimal risk. Classified as Read with low severity.
From the tool's definition Tool description states it 'Get[s] Steam player profile information including name, avatar, status, and current game' — purely retrieving/querying publicly available player data with no modification or side effects.
Attacks that exploit this kind of access
Get Steam player profile information including name, avatar, status, and current game. 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_player_summary: 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_player_summary 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_player_summary 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_player_summary. 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_player_summary 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 →