Get leaderboard scores and rankings for a Steam app. Pass the numeric leaderboard ID from your Steamworks dashboard, not the name. Uses the partner API (partner.steam-api.com) which requires a publisher API key with server IP allowlisted in Steamworks. Supports global, around-user, and friends-on...
AI agents call steam_getLeaderboardEntries 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 queries existing leaderboard data from Steam with no side effects. It provides read-only access to publicly available rankings information. The requirement for a publisher API key and IP allowlisting is a security measure, not an indication of destructive or execute capability. Even with misuse, an agent could only retrieve data, not modify game state, delete records, or trigger unauthorized actions.
From the tool's definition Tool retrieves 'leaderboard scores and rankings' with no modification capabilities. Description explicitly states 'Get' operation and 'Views' (read-only perspectives). No create, update, delete, or execute operations mentioned.
Attacks that exploit this kind of access
Get leaderboard scores and rankings for a Steam app. Pass the numeric leaderboard ID from your Steamworks dashboard, not the name. Uses the partner API (partner.steam-api.com) which requires a publisher API key with server IP allowlisted in Steamworks. Supports global, around-user, and friends-only views. 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_getLeaderboardEntries: 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_getLeaderboardEntries 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_getLeaderboardEntries 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_getLeaderboardEntries. 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_getLeaderboardEntries 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 →