Get the current number of concurrent players for a Steam app. No API key required.
AI agents call steam_getPlayerCount 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 and returns data (current player count) without side effects, making it a Read operation. The blast radius is minimal—incorrect usage would only return inaccurate player statistics, causing no harm to systems or data. Low severity reflects the informational nature of the query.
From the tool's definition Tool name 'steam_getPlayerCount' and description 'Get the current number of concurrent players for a Steam app' indicate a retrieval operation that queries public Steam statistics without modification or execution.
Attacks that exploit this kind of access
Get the current number of concurrent players for a Steam app. No API key required. 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_getPlayerCount: 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_getPlayerCount 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_getPlayerCount 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_getPlayerCount. 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_getPlayerCount 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 →