steam_charts_most_played
Get Steam's weekly most-played games chart. Returns Steam's weekly most-played chart: the top games ranked by peak concurrent players over the last week (rank, appid, previous-week rank, peak players). By default each row is enriched with the game name and review summary via a batch lookup; pass ...
This record as markdown: /tools/crawlora-mcp/steam-charts-most-played.md
What steam_charts_most_played does on Crawlora
AI agents call steam_charts_most_played 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 |
|---|---|---|---|
l | string | — | Steam store language name for name enrichment |
cc | string | — | Store country code (ISO) for name enrichment |
enrich | boolean | — | Attach game name and review summary to each rank |
Parameters from the server's own tool schema.
Why steam_charts_most_played is rated Low
This tool queries and retrieves publicly available Steam gaming statistics without any side effects, modifications, deletions, or external operations. It performs data retrieval only, fitting the Read category. Severity is low because the data is public, non-sensitive gaming statistics with no blast radius if accessed or cached inappropriately.
From the tool's definition Tool retrieves public Steam charts data with 'Get', 'Returns', and 'batch lookup' for enrichment. Description emphasizes 'Credential-free public Steam WebAPI JSON' with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs steam_charts_most_played 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_charts_most_played, this is the rule to start with:
steam_charts_most_played 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_charts_most_played call is checked against it from then on.
Questions about steam_charts_most_played
Get Steam's weekly most-played games chart. Returns Steam's weekly most-played chart: the top games ranked by peak concurrent players over the last week (rank, appid, previous-week rank, peak players). By default each row is enriched with the game name and review summary via a batch lookup; pass enrich=false for the raw ranked app ids only. 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_charts_most_played accepts 3 parameters: l, cc, enrich. 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_charts_most_played: 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_charts_most_played 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_charts_most_played 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_charts_most_played. 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_charts_most_played 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