get_invoice_payments
AI agents call get_invoice_payments to retrieve information from Clockify Time Tracking without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is unambiguously associated with retrieval operations. While the description is empty, the tool name and the financial domain context (invoicing system) indicate this retrieves payment information rather than creating, modifying, or deleting data. This is a Read operation with low blast radius—querying invoice payments poses minimal risk compared to payment creation or deletion.
From the tool's definition Tool name 'get_invoice_payments' indicates a retrieval operation with the 'get_' prefix, which is a standard Read pattern.
Attacks that exploit this kind of access
get_invoice_payments. It is categorised as a Read tool in the Clockify Time Tracking MCP Server, which means it retrieves data without modifying state.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for get_invoice_payments: 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.
get_invoice_payments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_invoice_payments 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 get_invoice_payments. 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.
get_invoice_payments 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 →