mark_invoice_sent
Mark an invoice as sent to the customer (transitions DRAFT → OPEN). Use after delivering the invoice via email or share link. Idempotent.
This record as markdown: /tools/io-favcrm-favcrm/mark-invoice-sent.md
What mark_invoice_sent does on FavCRM
AI agents use mark_invoice_sent to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
invoiceId | string | Yes | Invoice ID |
Parameters from the server's own tool schema.
Why mark_invoice_sent is rated Medium
This tool modifies invoice status in the CRM system, which is a reversible write operation affecting financial records. While it changes the state of an invoice (a financial document), it does not move money or create new financial obligations—it only marks that an invoice has been sent, changing its internal status.
From the tool's definition Tool transitions invoice state from DRAFT to OPEN ("transitions DRAFT → OPEN"), indicating a state modification of financial data that creates business obligations.
Attacks that exploit this kind of access
The rule that runs mark_invoice_sent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_invoice_sent, this is the rule to start with:
mark_invoice_sent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every mark_invoice_sent call is checked against it from then on.
Questions about mark_invoice_sent
Mark an invoice as sent to the customer (transitions DRAFT → OPEN). Use after delivering the invoice via email or share link. Idempotent. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mark_invoice_sent accepts 1 parameter: invoiceId. Required: invoiceId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for mark_invoice_sent: 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 FavCRM. Nothing to install.
mark_invoice_sent 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 mark_invoice_sent 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 mark_invoice_sent. 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.
mark_invoice_sent is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue