complete_and_invoice_milestone
Mark a consulting deliverable as delivered and auto-create a draft invoice for the milestone. Combines status update and invoice generation in one step.
This record as markdown: /tools/app-businys-mcp-server/complete-and-invoice-milestone.md
What complete_and_invoice_milestone does on Businys
AI agents use complete_and_invoice_milestone 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 complete_and_invoice_milestone is rated Medium
The tool updates a milestone status and creates a draft invoice. Both are reversible write operations — the invoice is a draft (not yet sent or paid), and status updates can presumably be undone. No money is moved, no data is destroyed. The most severe applicable category is Write.
From the tool's definition Mark a consulting deliverable as delivered and auto-create a draft invoice for the milestone. Combines status update and invoice generation in one step.
Attacks that exploit this kind of access
The rule that runs complete_and_invoice_milestone 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 complete_and_invoice_milestone, this is the rule to start with:
complete_and_invoice_milestone 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 complete_and_invoice_milestone call is checked against it from then on.
Questions about complete_and_invoice_milestone
Mark a consulting deliverable as delivered and auto-create a draft invoice for the milestone. Combines status update and invoice generation in one step. 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 complete_and_invoice_milestone: 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.
complete_and_invoice_milestone 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 complete_and_invoice_milestone 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 complete_and_invoice_milestone. 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.
complete_and_invoice_milestone 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