list_customer_signals
List first-party customer signals (the store live plays fire from) for the workspace, or scope to one company/person via subjectType + subjectId. Distinct from get_intent_signals (third-party intent).
This record as markdown: /tools/adrata-starfield-mcp/list-customer-signals.md
What list_customer_signals does on Starfield
AI agents call list_customer_signals 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 | — | Page size (default 50, max 500) |
since | string | — | ISO timestamp lower bound on observed_at |
until | string | — | ISO timestamp upper bound on observed_at |
cursor | string | — | Opaque cursor from a previous page |
source | string | — | Filter by ingest source, e.g. linkedin_engager |
minScore | number | — | Only signals at or above this score |
subjectId | string | — | Company or person ID to scope signals to |
signalType | string | — | Filter by signal type |
subjectType | string | — | Scope to a subject kind; pair with subjectId |
Parameters from the server's own tool schema.
Why list_customer_signals is rated Low
Even though list_customer_signals 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 list_customer_signals 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 list_customer_signals, this is the rule to start with:
list_customer_signals 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 list_customer_signals call is checked against it from then on.
Questions about list_customer_signals
List first-party customer signals (the store live plays fire from) for the workspace, or scope to one company/person via subjectType + subjectId. Distinct from get_intent_signals (third-party intent). It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
list_customer_signals accepts 9 parameters: limit, since, until, cursor, source, minScore, subjectId, signalType, subjectType. 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 list_customer_signals: 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.
list_customer_signals 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_customer_signals 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_customer_signals. 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_customer_signals 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