get_company_invoices
One account's ingested ERP invoices (latest snapshot per invoice) and the catalog products they resolve to. Read-only and workspace-scoped. An account with no ingested invoices returns an empty list — that is the honest answer, not a zero total. The API route has no pagination; limit/offset are a...
This record as markdown: /tools/adrata-starfield-mcp/get-company-invoices.md
What get_company_invoices does on Starfield
AI agents call get_company_invoices to retrieve information from Starfield 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 |
|---|---|---|---|
limit | number | — | Max invoices returned (client-side cap, default 200) |
offset | number | — | Invoices to skip (client-side) |
company_id | string | Yes | Adrata company id |
Parameters from the server's own tool schema.
Why get_company_invoices is rated Low
Even though get_company_invoices 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 get_company_invoices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_company_invoices, this is the rule to start with:
get_company_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 Starfield, apply this rule, and every get_company_invoices call is checked against it from then on.
Questions about get_company_invoices
One account's ingested ERP invoices (latest snapshot per invoice) and the catalog products they resolve to. Read-only and workspace-scoped. An account with no ingested invoices returns an empty list — that is the honest answer, not a zero total. The API route has no pagination; limit/offset are applied client-side to the invoices array (default cap 200 rows). It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
get_company_invoices accepts 3 parameters: limit, offset, company_id. Required: company_id. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for get_company_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 Starfield. Nothing to install.
get_company_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 get_company_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 get_company_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.
get_company_invoices is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue