Get user's recent Steam gaming activity.
AI agents call get_steam_recent_activity 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 retrieves historical gaming activity data from Steam without modifying, creating, or deleting any information. It is a straightforward read operation querying personal user data. The severity is low because even if accessed by an unauthorized AI agent, viewing past gaming activity presents minimal risk compared to other categories—no financial impact, no destructive operations, and no code execution.
From the tool's definition Tool name explicitly states 'get' (retrieve operation) and description states 'Get user's recent Steam gaming activity' — a data retrieval operation with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access get_steam_recent_activity 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_steam_recent_activity:
{
"version": "1",
"default": "deny",
"tools": {
"get_steam_recent_activity": {}
}
}get_steam_recent_activity 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 user's recent Steam gaming activity. 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_steam_recent_activity: 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_steam_recent_activity 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_steam_recent_activity 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_steam_recent_activity. 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_steam_recent_activity 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.