AI agents call get_player_bans to retrieve information from Mcp Steam without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data about a player's ban status—a straightforward query operation with no side effects. It does not create, modify, delete, or execute any actions; it simply reads public or account-accessible ban information from Steam. The low severity reflects minimal blast radius even if misused by an agent, as it only discloses information rather than affecting game state, accounts, or financial operations.
From the tool's definition Tool name 'get_player_bans' and description 'Get ban status for a Steam player' indicate a read-only query operation that retrieves existing ban status information without modification.
Attacks that exploit this kind of access
Get ban status for a Steam player. It is categorised as a Read tool in the Mcp Steam MCP Server, which means it retrieves data without modifying state.
Register the Mcp Steam 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 Mcp Steam. 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 Mcp Steam MCP server (obrien-matthew/mcp-steam). 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 →