activitywatch_update_category
Update an existing ActivityWatch category by its name path. Replaces the matching category with new values.
This record as markdown: /tools/8bitgentleman-activitywatch-mcp-server/activitywatch-update-category.md
What activitywatch_update_category does on ActivityWatch MCP Server
AI agents use activitywatch_update_category to create or update resources in ActivityWatch MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ActivityWatch MCP Server environment.
Why activitywatch_update_category is rated Medium
This tool modifies category metadata within ActivityWatch in a reversible manner. It changes configuration/categorization rules but does not delete data, execute code, or affect financial systems. The impact is limited to user-defined category definitions.
From the tool's definition Tool description states 'Update an existing ActivityWatch category by its name path. Replaces the matching category with new values.' The verb 'Update' and 'Replaces' indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs activitywatch_update_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_update_category, this is the rule to start with:
activitywatch_update_category stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_update_category call is checked against it from then on.
Questions about activitywatch_update_category
Update an existing ActivityWatch category by its name path. Replaces the matching category with new values. It is categorised as a Write tool in the ActivityWatch MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ActivityWatch MCP Server MCP server in PolicyLayer and add a rule for activitywatch_update_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_update_category is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the activitywatch_update_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_update_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_update_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.
This server
Across the catalogue