publish_assignments
AI agents use publish_assignments 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.
Publishing assignments likely makes them visible or active to team members, modifying their state irreversibly within the system. This is a write operation (state change) rather than destructive (no deletion), but affects potentially multiple records with organizational impact.
From the tool's definition Tool name 'publish_assignments' indicates modification of assignment records; sibling tools like 'create_assignment' and 'change_invoice_status' confirm this server performs write operations on organizational data.
Attacks that exploit this kind of access
publish_assignments. 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 publish_assignments: 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.
publish_assignments 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 publish_assignments 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 publish_assignments. 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.
publish_assignments 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 →