list_actions
List actions with filters. Use to answer "what did X do this week?" Use viewMode:"leader" to see the whole team's activity rather than only your own.
This record as markdown: /tools/adrata-starfield-mcp/list-actions.md
What list_actions does on Starfield
AI agents call list_actions 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 |
|---|---|---|---|
page | number | — | Page number |
type | string | — | |
limit | number | — | Results per page (default 25) |
sortBy | string | — | |
status | string | — | |
personId | string | — | |
priority | string | — | |
viewMode | string | — | seller = your own actions (default). leader = the whole team's actions; requires workspace admin. |
companyId | string | — | |
sortOrder | string | — | |
assignedTo | string | — |
Parameters from the server's own tool schema.
Why list_actions is rated Low
Even though list_actions 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.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs list_actions 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_actions, this is the rule to start with:
list_actions 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_actions call is checked against it from then on.
Questions about list_actions
List actions with filters. Use to answer "what did X do this week?" Use viewMode:"leader" to see the whole team's activity rather than only your own. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
list_actions accepts 11 parameters: page, type, limit, sortBy, status, personId, priority, viewMode, companyId, sortOrder, assignedTo. 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_actions: 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_actions 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_actions 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_actions. 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_actions 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