activitywatch-get-events
AI agents call activitywatch-get-events 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 event data from ActivityWatch, a time-tracking system. The 'get' verb combined with context of sibling read operations (list-buckets, query-examples, run-query) confirms this is a data retrieval operation with no side effects. While the description is empty, the tool name and server context strongly indicate a query/fetch operation typical of Read category tools.
From the tool's definition Tool name 'activitywatch-get-events' indicates retrieval of event data. The tool is grouped with other query and list operations (activitywatch-list-buckets, activitywatch-query-examples, activitywatch-run-query) suggesting read-only access patterns.
Attacks that exploit this kind of access
activitywatch-get-events. 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 (jelloeater/activitywatch-mcp-server-py). 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 →