create_expense
AI agents use create_expense 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 creates a new expense entry, which is a reversible write operation (expenses can typically be edited or deleted). While the description is empty, the naming convention and context of sibling tools strongly indicate this creates expense records in a financial tracking system.
From the tool's definition Tool name 'create_expense' indicates creation of a new expense record. Sibling tools on the same server include 'add_invoice_item', 'add_invoice_payment', and 'create_expense_category', all of which are write operations that create or modify financial/expense…
Attacks that exploit this kind of access
create_expense. 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 create_expense: 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.
create_expense 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 create_expense 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 create_expense. 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.
create_expense 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 →