Get code examples and documentation for creating Steam multiplayer lobbies. Lobby creation is a client-side SDK operation (ISteamMatchmaking) and cannot be done via HTTP API. This tool returns ready-to-use code for C++, C#, and GDScript.
AI agents call steam_createLobby 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.
Despite the name 'createLobby', the tool's actual function is to return documentation and code snippets. It explicitly states that lobby creation 'cannot be done via HTTP API' and that it 'returns ready-to-use code'. No actual creation or modification occurs; it is purely a read/query operation returning static content.
From the tool's definition returns ready-to-use code for C++, C#, and GDScript — this tool only retrieves documentation and code examples, it does not actually create any lobby or perform any side effects
Attacks that exploit this kind of access
Get code examples and documentation for creating Steam multiplayer lobbies. Lobby creation is a client-side SDK operation (ISteamMatchmaking) and cannot be done via HTTP API. This tool returns ready-to-use code for C++, C#, and GDScript. 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 steam_createLobby: 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.
steam_createLobby 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 steam_createLobby 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 steam_createLobby. 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.
steam_createLobby is provided by the Steam MCP Server MCP server (tmhsdigital/steam-mcp). 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 →