Low Risk

get_steam_recent_games

Get recently played games for ${this.config.steam_id}

How to control get_steam_recent_games ↓

What get_steam_recent_games does on Mcp Me

AI agents call get_steam_recent_games to retrieve information from Mcp Me without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_steam_recent_games needs a policy

This tool queries public or personal Steam gaming history data and returns it without any side effects. It fits the Read category as a data retrieval operation. Severity is low because the information exposed (game play history) is typically non-sensitive personal data that the user has chosen to store on Steam, and exposure causes no operational harm.

From the tool's definition Tool name begins with 'get_' and description indicates it retrieves recently played games. No modification, deletion, or execution of code/commands is implied. The action is purely informational retrieval from a Steam profile.

Documented attack patterns abuse exactly the kind of access get_steam_recent_games gives an agent:

How to control get_steam_recent_games

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Me, and nothing reaches the server without passing your rules. This is the rule we recommend for get_steam_recent_games:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_steam_recent_games": {}
  }
}

get_steam_recent_games is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Me — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_steam_recent_games

What does the get_steam_recent_games tool do? +

Get recently played games for ${this.config.steam_id}. It is categorised as a Read tool in the Mcp Me MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_steam_recent_games? +

Register the Mcp Me MCP server in PolicyLayer and add a rule for get_steam_recent_games: 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 Me. Nothing to install.

What risk level is get_steam_recent_games? +

get_steam_recent_games is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_steam_recent_games? +

Yes. Add a rate_limit block to the get_steam_recent_games 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.

How do I block get_steam_recent_games completely? +

Set action: deny in the PolicyLayer policy for get_steam_recent_games. 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.

What MCP server provides get_steam_recent_games? +

get_steam_recent_games is provided by the Mcp Me MCP server (paladini/mcp-me). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Me tool call.

Start from Mcp Me, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

17 Mcp Me tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.