steam_players
Get the current concurrent-player count for a Steam app. Returns the official current concurrent-players count for an app. Credential-free public Steam WebAPI JSON.
This record as markdown: /tools/crawlora-mcp/steam-players.md
What steam_players does on Crawlora
AI agents call steam_players to retrieve information from Crawlora 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 |
|---|---|---|---|
appid | string | Yes | Numeric Steam app id |
Parameters from the server's own tool schema.
Why steam_players is rated Low
This tool only retrieves publicly available data from Steam's API. It has no side effects, does not modify data, execute code, delete anything, or move money. The read-only nature is confirmed by the credential-free access to public API endpoints and the singular retrieval action described.
From the tool's definition Tool description explicitly states it 'Get[s] the current concurrent-player count' and 'Returns the official current concurrent-players count for an app' from 'public Steam WebAPI JSON' with no modification capability.
Attacks that exploit this kind of access
The rule that runs steam_players safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For steam_players, this is the rule to start with:
steam_players 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 Crawlora, apply this rule, and every steam_players call is checked against it from then on.
Questions about steam_players
Get the current concurrent-player count for a Steam app. Returns the official current concurrent-players count for an app. Credential-free public Steam WebAPI JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
steam_players accepts 1 parameter: appid. Required: appid. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for steam_players: 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 Crawlora. Nothing to install.
steam_players 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_players 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_players. 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_players is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue