AI agents call my_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 personal gaming activity history from Steam. It performs a read-only query with no side effects—it does not create, modify, delete, or execute any operations. While it accesses personal data (gaming history), the operation itself is purely informational retrieval, making it a Read category tool.
From the tool's definition Tool name 'my_steam_recent_activity' and description 'Get my recent Steam gaming activity' indicate retrieval of historical data with no modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access my_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 my_steam_recent_activity:
{
"version": "1",
"default": "deny",
"tools": {
"my_steam_recent_activity": {}
}
}my_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 my 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 my_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.
my_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 my_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 my_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.
my_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.