list_invoices
List the caller's invoices (newest first), optionally filtered by status (draft/sent/paid/void). Each entry includes its computed overdue flag.
This record as markdown: /tools/com-meta-council-decision-intelligence/list-invoices.md
What list_invoices does on Meta Council
AI agents call list_invoices 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 |
|---|---|---|---|
status | string | — | Optional status filter. |
Parameters from the server's own tool schema.
Why list_invoices is rated Low
This is a Read operation: it retrieves invoice records without creating, modifying, or deleting them. Severity is medium rather than low because invoices contain sensitive financial information (amounts, dates, payment status, overdue flags) whose disclosure could enable downstream financial attacks or decision-making.
From the tool's definition Tool name is 'list_invoices' and description states it 'List[s] the caller's invoices' with optional filtering by status. No modification, deletion, or financial transaction occurs—it only retrieves and queries invoice data.
Attacks that exploit this kind of access
The rule that runs list_invoices 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 list_invoices, this is the rule to start with:
list_invoices 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 list_invoices call is checked against it from then on.
Questions about list_invoices
List the caller's invoices (newest first), optionally filtered by status (draft/sent/paid/void). Each entry includes its computed overdue flag. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_invoices accepts 1 parameter: status. 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 list_invoices: 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.
list_invoices 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 list_invoices 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 list_invoices. 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.
list_invoices 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