Get what games your Steam friends are currently playing.
AI agents call get_friends_current_games to retrieve information from PersonalizationMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves the current gaming activity of Steam friends. It performs a read-only operation with no side effects, no code execution, and no data modification. The only risk is potential privacy concern around friend activity visibility, which is already controlled by Steam's permission model. Blast radius is minimal—misuse would only expose already-visible social information.
From the tool's definition Tool name is 'get_friends_current_games' and description states 'Get what games your Steam friends are currently playing' — purely retrieves data with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_friends_current_games gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PersonalizationMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_friends_current_games:
{
"version": "1",
"default": "deny",
"tools": {
"get_friends_current_games": {}
}
}get_friends_current_games is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get what games your Steam friends are currently playing. It is categorised as a Read tool in the PersonalizationMCP MCP Server, which means it retrieves data without modifying state.
Register the Personalization MCP server in PolicyLayer and add a rule for get_friends_current_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 PersonalizationMCP. Nothing to install.
get_friends_current_games 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_friends_current_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.
Set action: deny in the PolicyLayer policy for get_friends_current_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.
get_friends_current_games is provided by the Personalization MCP server (yangliangwei/personalizationmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 PersonalizationMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 PersonalizationMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.