Check if a player is currently playing a game via Steam Family Sharing
AI agents call is_playing_shared_game 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 Steam's API to retrieve the current play status of a player using Family Sharing. It retrieves information without modifying any data, executing code, or triggering external side effects. It is a straightforward informational query similar to other sibling tools like get_friends_list and get_achievements.
From the tool's definition Tool name 'is_playing_shared_game' and description 'Check if a player is currently playing a game' indicates a query operation that retrieves current status information.
Attacks that exploit this kind of access
Check if a player is currently playing a game via Steam Family Sharing. 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 is_playing_shared_game: 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.
is_playing_shared_game 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 is_playing_shared_game 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 is_playing_shared_game. 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.
is_playing_shared_game 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 →