update_assignment
AI agents use update_assignment to create or update resources in Clockify Time Tracking — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clockify Time Tracking environment.
The tool modifies existing assignment records (reversible operation), fitting the Write category. Severity is medium because misuse could alter work assignments affecting billing, project tracking, or resource allocation, but changes are typically reversible. Confidence is 0.85 rather than higher due to the empty description, though the name and context strongly suggest a write operation.
From the tool's definition Tool name 'update_assignment' indicates modification of assignment data. Context shows this is part of Clockify's time-tracking system where assignments link users to projects.
Attacks that exploit this kind of access
update_assignment. It is categorised as a Write tool in the Clockify Time Tracking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for update_assignment: 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 Clockify Time Tracking. Nothing to install.
update_assignment 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 update_assignment 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 update_assignment. 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.
update_assignment is provided by the Clockify Time Tracking MCP server (pypi:clockify-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 →