Get progress on community badge crafting (trading cards)
AI agents call get_badge_progress to retrieve information from Steam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves badge crafting progress information from a player's Steam account. It is a read-only query operation with no side effects, no code execution, no data modification, and no financial impact. The worst-case misuse would be unauthorized information disclosure about a player's badge progress, which has minimal blast radius.
From the tool's definition Tool name 'get_badge_progress' and description 'Get progress on community badge crafting (trading cards)' indicate a retrieval operation that queries existing badge/trading card progress data without modifying or deleting anything.
Attacks that exploit this kind of access
Get progress on community badge crafting (trading cards). It is categorised as a Read tool in the Steam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Steam MCP Server MCP server in PolicyLayer and add a rule for get_badge_progress: 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 Steam MCP Server. Nothing to install.
get_badge_progress 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 get_badge_progress 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 get_badge_progress. 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.
get_badge_progress is provided by the Steam MCP Server MCP server (sharkusmanch/steam-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →