get_invoice
Fetch a single invoice with line items, payment history, and customer detail.
This record as markdown: /tools/io-favcrm-favcrm/get-invoice.md
What get_invoice does on FavCRM
AI agents call get_invoice to retrieve information from FavCRM 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 |
|---|---|---|---|
invoiceId | string | Yes | Invoice ID |
Parameters from the server's own tool schema.
Why get_invoice is rated Low
This tool retrieves invoice data (line items, payment history, customer details) without creating, modifying, deleting, or executing operations. It is purely a query operation with no side effects, fitting the Read category. Severity is low because exposure of invoice data has limited blast radius in typical CRM misuse scenarios (no financial transactions, deletions, or code execution occur).
From the tool's definition Tool name 'get_invoice' and description 'Fetch a single invoice' — the verb 'fetch' indicates data retrieval with no modification or destructive action.
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 FavCRM, 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 FavCRM, apply this rule, and every get_invoice call is checked against it from then on.
Questions about get_invoice
Fetch a single invoice with line items, payment history, and customer detail. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_invoice accepts 1 parameter: invoiceId. Required: invoiceId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue