search_steam_store
Search the Steam store for games by name.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/search-steam-store.md
What search_steam_store does on UnClick
AI agents call search_steam_store to retrieve information from UnClick 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 | — | Country code for pricing |
term | string | Yes | Search term |
Parameters from the server's own tool schema.
Why search_steam_store is rated Low
This tool queries the Steam store database and returns matching games. It performs a read-only search operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only retrieve unwanted game information, which poses no security or operational risk.
From the tool's definition Tool name is 'search_steam_store' and description states 'Search the Steam store for games by name.' The verb 'search' combined with 'for games by name' indicates a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_steam_store safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_steam_store, this is the rule to start with:
search_steam_store 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 UnClick, apply this rule, and every search_steam_store call is checked against it from then on.
Questions about search_steam_store
Search the Steam store for games by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
search_steam_store accepts 3 parameters: l, cc, term. Required: term. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for search_steam_store: 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 UnClick. Nothing to install.
search_steam_store 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 search_steam_store 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 search_steam_store. 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.
search_steam_store is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue