AI agents call get_recently_played to retrieve information from Mcp Steam without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical gameplay data from the user's Steam account without modifying, deleting, or executing anything. It is purely informational and carries minimal risk—an agent using this tool can only retrieve data about games the user has already played. No financial transactions, code execution, or data modification occurs.
From the tool's definition Tool name 'get_recently_played' and description 'Get your recently played Steam games' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying a user's game history confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get your recently played Steam games (last 2 weeks). It is categorised as a Read tool in the Mcp Steam MCP Server, which means it retrieves data without modifying state.
Register the Mcp 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 Mcp 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 Mcp Steam MCP server (obrien-matthew/mcp-steam). 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 →