Get the user
AI agents call get_current_activity to retrieve information from ActivityWatch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current activity data without modifying, executing code, deleting data, or moving money. It is a Read operation. Severity is medium because exposure of real-time computer activity including current app, window title, or active process could reveal sensitive information (passwords in text fields, private conversations, confidential work), though the impact is primarily informational rather than…
From the tool's definition Tool name is 'get_current_activity' and description states 'Get the user' activity. The sibling tools (get_browser_history, get_category_time, get_day_summary, get_timeline) are all read-only queries.
Attacks that exploit this kind of access
Get the user. It is categorised as a Read tool in the ActivityWatch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ActivityWatch MCP Server MCP server in PolicyLayer and add a rule for get_current_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 ActivityWatch MCP Server. Nothing to install.
get_current_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_current_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_current_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_current_activity is provided by the ActivityWatch MCP Server MCP server (jm-404/activitywatch-mcp). 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 →