Get game servers running at a specific IP address
AI agents call get_servers_at_address 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.
The tool performs a read-only lookup of game server information based on IP address input. While IP scanning could be used for reconnaissance, this tool itself does not execute code, modify data, delete resources, or move funds. It simply retrieves and returns publicly queryable server information via the Steam Web API, consistent with other Read tools on this server like get_friends_list and get_game_details.
From the tool's definition Tool retrieves information about game servers at an IP address ("Get game servers running at a specific IP address"). This is a query/lookup operation with no data modification, deletion, or external state changes.
Attacks that exploit this kind of access
Get game servers running at a specific IP address. 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_servers_at_address: 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_servers_at_address 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_servers_at_address 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_servers_at_address. 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_servers_at_address 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 →