activitywatch_delete_category
Delete an ActivityWatch category by its name path.
This record as markdown: /tools/8bitgentleman-activitywatch-mcp-server/activitywatch-delete-category.md
What activitywatch_delete_category does on ActivityWatch MCP Server
AI agents call activitywatch_delete_category to permanently remove resources in ActivityWatch MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why activitywatch_delete_category is rated Critical
This tool permanently removes a category from ActivityWatch, which cannot be undone. Deletion is irreversible and represents data loss. While the scope is limited to category metadata (not entire event logs), it still qualifies as Destructive rather than Write, as the operation cannot be reversed.
From the tool's definition Tool name contains 'delete' and description states 'Delete an ActivityWatch category by its name path.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs activitywatch_delete_category 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_delete_category, this is the rule to start with:
activitywatch_delete_category is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ActivityWatch MCP Server, apply this rule, and every activitywatch_delete_category call is checked against it from then on.
Questions about activitywatch_delete_category
Delete an ActivityWatch category by its name path. It is categorised as a Destructive tool in the ActivityWatch MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ActivityWatch MCP Server MCP server in PolicyLayer and add a rule for activitywatch_delete_category: 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_delete_category is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the activitywatch_delete_category 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_delete_category. 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_delete_category 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.
Across the catalogue