convert_deal_to_invoice
Create a draft invoice from one of the caller's deals: one line item for the deal's amount, client_name defaulted from the deal's company/title. deal_id is required.
This record as markdown: /tools/com-meta-council-decision-intelligence/convert-deal-to-invoice.md
What convert_deal_to_invoice does on Meta Council
AI agents use convert_deal_to_invoice to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | |
deal_id | string | Yes | |
due_date | string | — | ISO date YYYY-MM-DD. |
tax_rate | number | — | |
client_name | string | — | Defaults to the deal's company or title. |
client_email | string | — | |
payment_terms | string | — |
Parameters from the server's own tool schema.
Why convert_deal_to_invoice is rated Medium
While invoicing is financially adjacent, the tool creates a *draft* invoice, not an actual payment or financial transaction. It is reversible (draft status implies it has not been finalized or submitted), making it Write rather than Financial. However, severity is high because invoices are critical financial documents; misuse could lead to incorrect billing, audit issues, or fraud.
From the tool's definition Tool description states 'Create a draft invoice' — this is a create operation that modifies financial records. The presence of sibling tools like 'add_invoice_line_item' and the term 'draft invoice' confirm this creates new invoice data.
Attacks that exploit this kind of access
The rule that runs convert_deal_to_invoice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_deal_to_invoice, this is the rule to start with:
convert_deal_to_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 Meta Council, apply this rule, and every convert_deal_to_invoice call is checked against it from then on.
Questions about convert_deal_to_invoice
Create a draft invoice from one of the caller's deals: one line item for the deal's amount, client_name defaulted from the deal's company/title. deal_id is required. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
convert_deal_to_invoice accepts 7 parameters: notes, deal_id, due_date, tax_rate, client_name, client_email, payment_terms. Required: deal_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for convert_deal_to_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 Meta Council. Nothing to install.
convert_deal_to_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 convert_deal_to_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 convert_deal_to_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.
convert_deal_to_invoice is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue