Get a detailed activity timeline for a specific day, showing what apps and windows were used chronologically
AI agents call get_timeline 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 merely queries and presents computer activity history in chronological order. It has no capability to modify, delete, or execute actions. While it accesses potentially sensitive data (activity logs), it is fundamentally a read-only retrieval function, making it categorically a Read tool with low severity because misuse would only expose information rather than cause destructive or harmful actions.
From the tool's definition Tool retrieves historical activity data ('Get a detailed activity timeline') without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get a detailed activity timeline for a specific day, showing what apps and windows were used chronologically. 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_timeline: 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_timeline 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_timeline 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_timeline. 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_timeline 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 →