create_invoice
Create a new invoice (draft \u2014 not visible to client until sent). Returns the new invoice ID, number, and public slug. Valid statuses: draft \u2192 sent \u2192 viewed \u2192 paid \u2192 overdue \u2192 voided.
This record as markdown: /tools/app-businys-mcp-server/create-invoice.md
What create_invoice does on Businys
AI agents use create_invoice to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why create_invoice is rated Medium
This tool creates a new invoice record in draft status. It is reversible (invoices can be voided, archived, or modified before sending), so it does not qualify as Destructive. It does not move money or create financial obligations until sent (status: sent → viewed → paid), so it is not Financial at the creation stage.
From the tool's definition Tool description states 'Create a new invoice (draft — not visible to client until sent)' and 'Returns the new invoice ID, number, and public slug.' The verb 'Create' and the clear data creation operation indicate write functionality.
Attacks that exploit this kind of access
The rule that runs create_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_invoice, this is the rule to start with:
create_invoice 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 Businys, apply this rule, and every create_invoice call is checked against it from then on.
Questions about create_invoice
Create a new invoice (draft \u2014 not visible to client until sent). Returns the new invoice ID, number, and public slug. Valid statuses: draft \u2192 sent \u2192 viewed \u2192 paid \u2192 overdue \u2192 voided. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for create_invoice: 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 Businys. Nothing to install.
create_invoice 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_invoice 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_invoice. 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_invoice is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue