create_invoice
Create a draft invoice owned by the caller for a client, optionally seeded with line items and linked to an existing deal. Totals (subtotal/tax/total) are computed from the line items and tax_rate. The invoice starts in status 'draft' — call send_invoice to mark it sent.
This record as markdown: /tools/com-meta-council-decision-intelligence/create-invoice.md
What create_invoice does on Meta Council
AI agents use create_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 | — | Optional: link to an owned deal. |
currency | string | — | Three ASCII letters; normalized to uppercase (default USD). ISO membership is not checked. |
due_date | string | — | ISO date YYYY-MM-DD. |
tax_rate | number | — | Percentage, e.g. 8.5 for 8.5%. |
line_items | array | — | |
client_name | string | Yes | |
client_email | string | — | |
payment_terms | string | — | e.g. 'Net 30', 'Due on receipt'. |
Parameters from the server's own tool schema.
Why create_invoice is rated Medium
An AI agent can call create_invoice faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (12 properties)
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 Meta Council, 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 Meta Council, apply this rule, and every create_invoice call is checked against it from then on.
Questions about create_invoice
Create a draft invoice owned by the caller for a client, optionally seeded with line items and linked to an existing deal. Totals (subtotal/tax/total) are computed from the line items and tax_rate. The invoice starts in status 'draft' — call send_invoice to mark it sent. 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.
create_invoice accepts 9 parameters: notes, deal_id, currency, due_date, tax_rate, line_items, client_name, client_email, payment_terms. Required: client_name. 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 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 Meta Council. 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 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