Record a payment received against an invoice.
AI agents use add_invoice_payment to commit financial operations through Clockify Time Tracking — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Recording a payment against an invoice is a financial operation that modifies accounting/billing state. It could result in incorrect financial records if misused (e.g., marking unpaid invoices as paid, double-recording payments). This clearly falls under the Financial category as it involves committing financial obligations and records.
From the tool's definition 'Record a payment received against an invoice' — directly commits a financial transaction against an invoice record
Attacks that exploit this kind of access
Record a payment received against an invoice. It is categorised as a Financial tool in the Clockify Time Tracking MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for add_invoice_payment: 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_payment is a Financial 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 add_invoice_payment 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_payment. 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_payment 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 →