activitywatch_get_events
Get raw events from an ActivityWatch bucket
This record as markdown: /tools/8bitgentleman-activitywatch-mcp-server/activitywatch-get-events.md
What activitywatch_get_events does on ActivityWatch MCP Server
AI agents call activitywatch_get_events to retrieve information from ActivityWatch MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why activitywatch_get_events is rated Low
This tool retrieves historical event data from ActivityWatch buckets without modifying, deleting, or executing operations. While the sensitivity of retrieved data (browsing history, application usage patterns) warrants medium severity due to privacy implications if misused by an agent, the operation itself is read-only with no destructive or side effects. It belongs in the Read category as a data retrieval function.
From the tool's definition Tool name 'get_events' and description 'Get raw events from an ActivityWatch bucket' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs activitywatch_get_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ActivityWatch MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activitywatch_get_events, this is the rule to start with:
activitywatch_get_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ActivityWatch MCP Server, apply this rule, and every activitywatch_get_events call is checked against it from then on.
Questions about activitywatch_get_events
Get raw events from an ActivityWatch bucket. 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 activitywatch_get_events: 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.
activitywatch_get_events 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 activitywatch_get_events 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 activitywatch_get_events. 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.
activitywatch_get_events is provided by the ActivityWatch MCP Server MCP server (8bitgentleman/activitywatch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ActivityWatch MCP Server, and thousands of servers like it.
This server
Across the catalogue