sloan_status
What Sloan (the AI executive assistant) is doing: follow-up objective counts by state, work due soon, drafts awaiting approval, and recent events. Scope 'me' (default) shows your objectives; 'workspace' (managers only) shows every seller. Filter to one prospect with personId/companyId/recipientEm...
This record as markdown: /tools/adrata-starfield-mcp/sloan-status.md
What sloan_status does on Starfield
AI agents call sloan_status 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 |
|---|---|---|---|
scope | string | — | 'me' (default) or 'workspace' (manager/admin only) |
userId | string | — | View one seller's Sloan activity (manager/admin only) |
personId | string | — | Filter to objectives for this CRM person |
companyId | string | — | Filter to objectives for this CRM company |
rangeHours | number | — | Window for due-soon/recent events (default 24, max 2160) |
recipientEmail | string | — | Filter to objectives whose recipient email contains this text |
Parameters from the server's own tool schema.
Why sloan_status is rated Low
Even though sloan_status 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs sloan_status 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 sloan_status, this is the rule to start with:
sloan_status 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 sloan_status call is checked against it from then on.
Questions about sloan_status
What Sloan (the AI executive assistant) is doing: follow-up objective counts by state, work due soon, drafts awaiting approval, and recent events. Scope 'me' (default) shows your objectives; 'workspace' (managers only) shows every seller. Filter to one prospect with personId/companyId/recipientEmail. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
sloan_status accepts 6 parameters: scope, userId, personId, companyId, rangeHours, recipientEmail. 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 sloan_status: 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.
sloan_status 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 sloan_status 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 sloan_status. 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.
sloan_status 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