Get a player
AI agents call steam_getPlayerSummary 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 summary information (likely profile stats, level, avatar, etc.) from Steam's public API. It performs a read-only query with no side effects, no data modification, no code execution, and no financial impact. The blast radius of misuse is minimal—an attacker could gather player information but cannot modify accounts, execute commands, or cause harm.
From the tool's definition Tool name 'steam_getPlayerSummary' and description 'Get a player' indicate retrieval of player profile/summary data. The function appears to query existing player information without modification or deletion.
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_getPlayerSummary: 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_getPlayerSummary 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_getPlayerSummary 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_getPlayerSummary. 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_getPlayerSummary 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 →