AI agents call get_recently_played to retrieve information from Steam without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves game history and playtime statistics from the user's Steam library. It performs a read-only operation with no capability to modify, create, delete, or execute any actions. The data returned is informational only, making it a low-severity Read operation with no blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Get games played' with no modification, deletion, or execution capability. Returns historical play data and statistics only. Retrieves from Steam Web API without side effects.
Attacks that exploit this kind of access
Get games played in the last 2 weeks, with hours played this period and total. It is categorised as a Read tool in the Steam MCP Server, which means it retrieves data without modifying state.
Register the Steam MCP server in PolicyLayer and add a rule for get_recently_played: 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. Nothing to install.
get_recently_played 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_recently_played 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_recently_played. 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_recently_played is provided by the Steam MCP server (jkiley129/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 →