get_account_read
Get Adrata chat’s grounded no-loss account/deal read through the governed ToolDispatcher. Returns Known/Read/Ask, evidence, confidence, why-now, best move, alternatives, falsification criteria, and observable-evidence triangulation guardrails. Never infer IQ, age, college-as-IQ, or protected clas...
This record as markdown: /tools/adrata-starfield-mcp/get-account-read.md
What get_account_read does on Starfield
AI agents call get_account_read 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 |
|---|---|---|---|
companyId | string | — | Optional company/account ID for future account-read backend alignment. |
opportunityId | string | Yes | Opportunity/deal ID. Required until company-level account reads are integrated. |
includeEvidence | boolean | — | Whether to include evidence objects, default true. |
Parameters from the server's own tool schema.
Why get_account_read is rated Low
Even though get_account_read 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_account_read 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_account_read, this is the rule to start with:
get_account_read 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_account_read call is checked against it from then on.
Questions about get_account_read
Get Adrata chat’s grounded no-loss account/deal read through the governed ToolDispatcher. Returns Known/Read/Ask, evidence, confidence, why-now, best move, alternatives, falsification criteria, and observable-evidence triangulation guardrails. Never infer IQ, age, college-as-IQ, or protected classes. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
get_account_read accepts 3 parameters: companyId, opportunityId, includeEvidence. Required: opportunityId. 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_account_read: 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_account_read 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_account_read 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_account_read. 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_account_read 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