steam_featured_categories
Get Steam top sellers, new releases, specials and coming soon. Returns the storefront merchandising buckets for a region: specials, top_sellers, new_releases, and coming_soon, each with its item list. Credential-free public Steam storefront JSON.
This record as markdown: /tools/crawlora-mcp/steam-featured-categories.md
What steam_featured_categories does on Crawlora
AI agents call steam_featured_categories 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 | — | Language code |
cc | string | — | Store country code (ISO, selects currency) |
Parameters from the server's own tool schema.
Why steam_featured_categories is rated Low
This tool queries and returns public Steam store data with no side effects. It is purely informational retrieval, analogous to a search or list operation. No data is created, modified, deleted, or executed. Severity is low because misuse would only expose public information already available on Steam's website.
From the tool's definition Tool retrieves 'storefront merchandising buckets' from 'credential-free public Steam storefront JSON' — no modification, deletion, or execution occurs. Returns data on 'specials, top_sellers, new_releases, and coming_soon'.
Attacks that exploit this kind of access
The rule that runs steam_featured_categories 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_featured_categories, this is the rule to start with:
steam_featured_categories 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_featured_categories call is checked against it from then on.
Questions about steam_featured_categories
Get Steam top sellers, new releases, specials and coming soon. Returns the storefront merchandising buckets for a region: specials, top_sellers, new_releases, and coming_soon, each with its item list. Credential-free public Steam storefront JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
steam_featured_categories accepts 2 parameters: l, cc. 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_featured_categories: 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_featured_categories 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_featured_categories 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_featured_categories. 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_featured_categories 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