invoice_generator
Invoice Generator — Total a freelance invoice from line items {description, qty, rate} with optional discount and tax: subtotal, discount, tax, total, amount due.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/invoice-generator.md
What invoice_generator does on Gateway
AI agents call invoice_generator to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tax_pct | number | — | Sales-tax percent applied to the discounted subtotal |
discount | number | — | Discount amount (flat USD, or percent if discount_is_pct) |
line_items | array | Yes | Line items: [{description, qty, rate}] |
amount_paid | number | — | Amount already paid, subtracted from total for amount_due |
discount_is_pct | boolean | — | Treat discount as a percent of subtotal |
Parameters from the server's own tool schema.
Why invoice_generator is rated Low
Even though invoice_generator only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs invoice_generator safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invoice_generator, this is the rule to start with:
invoice_generator is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every invoice_generator call is checked against it from then on.
Questions about invoice_generator
Invoice Generator — Total a freelance invoice from line items {description, qty, rate} with optional discount and tax: subtotal, discount, tax, total, amount due. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
invoice_generator accepts 5 parameters: tax_pct, discount, line_items, amount_paid, discount_is_pct. Required: line_items. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for invoice_generator: 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 Gateway. Nothing to install.
invoice_generator is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the invoice_generator 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 invoice_generator. 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.
invoice_generator is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue