get_installed_base
Finance/expansion installed base: which accounts bought which SKUs (spend, invoice count, first/last purchase) from the customer's own ERP invoices, plus the accounts with no invoice at all. Read-only and scoped to your workspace. Always relay the returned coverage and note — zero invoices means ...
This record as markdown: /tools/adrata-starfield-mcp/get-installed-base.md
What get_installed_base does on Starfield
AI agents call get_installed_base 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 |
|---|---|---|---|
sku | string | — | Restrict to one vendor SKU |
limit | number | — | Rows per page (default 100, max 500) |
offset | number | — | |
company_id | string | — | Restrict to one account |
include_never_bought | boolean | — | Include accounts with no ingested invoice (default true) |
Parameters from the server's own tool schema.
Why get_installed_base is rated Low
Even though get_installed_base 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_installed_base 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_installed_base, this is the rule to start with:
get_installed_base 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_installed_base call is checked against it from then on.
Questions about get_installed_base
Finance/expansion installed base: which accounts bought which SKUs (spend, invoice count, first/last purchase) from the customer's own ERP invoices, plus the accounts with no invoice at all. Read-only and scoped to your workspace. Always relay the returned coverage and note — zero invoices means nothing has been ingested yet, NOT zero spend. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
get_installed_base accepts 5 parameters: sku, limit, offset, company_id, include_never_bought. 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_installed_base: 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_installed_base 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_installed_base 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_installed_base. 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_installed_base 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