add_invoice_item
AI agents use add_invoice_item 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.
Adding an invoice item creates or modifies invoice records, which is reversible (Write category). While invoices relate to financial operations, the tool itself adds line items rather than moving money or creating payment obligations, so it is Write not Financial. The empty description reduces confidence slightly, but the name and server context are clear.
From the tool's definition Tool name 'add_invoice_item' indicates creation/modification of invoice data. Sibling tools include 'add_invoice_payment' and 'change_invoice_status', confirming this server manages financial documents. Description is empty, limiting certainty.
Attacks that exploit this kind of access
add_invoice_item. 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 add_invoice_item: 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.
add_invoice_item 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 add_invoice_item 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 add_invoice_item. 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.
add_invoice_item 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 →