get_invoice
Fetch one of the caller's invoices by id, including its line items.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-invoice.md
What get_invoice does on Meta Council
AI agents call get_invoice to retrieve information from Meta Council 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 |
|---|---|---|---|
invoice_id | string | Yes | The invoice id. |
Parameters from the server's own tool schema.
Why get_invoice is rated Low
This tool retrieves invoice data for the caller without creating, modifying, or deleting anything. It is scoped to the caller's own invoices ('one of the caller's invoices'), limiting blast radius. While invoices may contain financial information, the tool itself does not move money, create financial obligations, or execute transactions—it only reads existing data.
From the tool's definition Tool name 'get_invoice' and description 'Fetch one of the caller's invoices by id' indicate retrieval of existing data without modification. The verb 'Fetch' is explicitly a Read operation.
Attacks that exploit this kind of access
The rule that runs get_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 get_invoice, this is the rule to start with:
get_invoice 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 Meta Council, apply this rule, and every get_invoice call is checked against it from then on.
Questions about get_invoice
Fetch one of the caller's invoices by id, including its line items. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_invoice accepts 1 parameter: invoice_id. Required: invoice_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 get_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.
get_invoice 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 get_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 get_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.
get_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