steam_tags

SERVERCrawlora SOURCEcrawlora-mcp

Medium RISK CLASS

Category Write

Parameters 120 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/steam-tags.md

WHAT IT DOES

What steam_tags does on Crawlora

AI agents use steam_tags to create or update resources in Crawlora, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crawlora environment.

Parameter	Type	Required	Description
`l`	string	—	Language code
`cc`	string	—	Store country code (ISO, selects currency)
`os`	string	—	Comma-separated platform filter subset of: win, mac, linux
`tags`	string	—	Comma-separated numeric community tag ids (all must match); resolve ids via /steam/tags/list
`count`	integer	—	Results per page (max 100)
`start`	integer	—	Result offset for pagination
`filter`	string	—	Curated preset applied within the other facets
`untags`	string	—	Comma-separated numeric community tag ids to EXCLUDE
`hidef2p`	boolean	—	Hide free-to-play titles
`sort_by`	string	—	Sort order
`maxprice`	string	—	Maximum price as whole cents in the cc currency, or the literal 'free'
`specials`	boolean	—	Only discounted titles

Parameters from the server's own tool schema.

RISK

Why steam_tags is rated Medium

An AI agent can call steam_tags faster than any human can review: one bad instruction and it creates or modifies resources in Crawlora by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (18 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs steam_tags 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_tags, this is the rule to start with:

steam_tags Rate-limited

steam_tags stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "steam_tags": {
      "limits": [
        {
          "counter": "steam_tags_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every steam_tags call is checked against it from then on.

FAQ

Questions about steam_tags

What does the steam_tags tool do? +

Browse the Steam store by community tag and store facets. Browses the store by the community-tag taxonomy (Roguelike, Metroidvania, Cozy...) and the store filter facets, with no free-text term. Filter by one or more tag ids, a store category id, platform (os), a maximum price, specials-only, and hide-free-to-play; sort and page the browse-rank rows. Each row includes its community tag ids (resolve names via /steam/tags/list). Pagination runs the full result set (total is the real, fully-pageable match count); paging past total returns an empty page. Credential-free public Steam storefront JSON. It is categorised as a Write tool in the Crawlora MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does steam_tags accept? +

steam_tags accepts 12 parameters: l, cc, os, tags, count, start, filter, untags, hidef2p, sort_by, maxprice, specials. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on steam_tags? +

Register the Crawlora MCP server in PolicyLayer and add a rule for steam_tags: 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.

What risk level is steam_tags? +

steam_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit steam_tags? +

Yes. Add a rate_limit block to the steam_tags 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.

How do I block steam_tags completely? +

Set action: deny in the PolicyLayer policy for steam_tags. 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.

What MCP server provides steam_tags? +

steam_tags 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.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

save_tags on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →