Check if a player has VAC bans, game bans, or trade bans
AI agents call get_player_bans 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 publicly available ban status data from the Steam Web API without modifying, deleting, or executing any operations. It is purely informational, similar to sibling tools like get_friends_list and get_game_details which are standard data retrieval operations. No reversible or irreversible modifications occur, and no code execution or financial transactions are involved.
From the tool's definition Tool name 'get_player_bans' and description 'Check if a player has VAC bans, game bans, or trade bans' indicate a query operation that retrieves ban status information with no side effects.
Attacks that exploit this kind of access
Check if a player has VAC bans, game bans, or trade bans. 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_player_bans: 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_player_bans 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_player_bans 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_player_bans. 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_player_bans 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 →