activitywatch-list-buckets
AI agents call activitywatch-list-buckets 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 lists buckets (likely containers for time-tracking data in ActivityWatch) without modifying, deleting, or executing anything. It is a straightforward retrieval operation. Confidence is slightly reduced due to empty description, but the naming pattern and sibling tools provide strong contextual evidence of read-only behavior.
From the tool's definition Tool name 'activitywatch-list-buckets' combined with sibling tools that include 'get-events', 'get-settings', and 'query-examples' indicates a read operation. The 'list' verb is characteristic of data retrieval with no side effects.
Attacks that exploit this kind of access
activitywatch-list-buckets. 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-list-buckets: 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-list-buckets 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-list-buckets 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-list-buckets. 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-list-buckets 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 →