check_inbox
Check your inbox for new replies. Cross-references with CRM contacts and active sequences to classify reply types (positive, OOO, meeting request, not interested) and suggest Next Moves. The "Did anyone get back to me?" tool.
This record as markdown: /tools/adrata-starfield-mcp/check-inbox.md
What check_inbox does on Starfield
AI agents call check_inbox 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 |
|---|---|---|---|
since | string | — | Check replies since date (ISO string, default: yesterday) |
Parameters from the server's own tool schema.
Why check_inbox is rated Low
Even though check_inbox 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 check_inbox 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 check_inbox, this is the rule to start with:
check_inbox 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 check_inbox call is checked against it from then on.
Questions about check_inbox
Check your inbox for new replies. Cross-references with CRM contacts and active sequences to classify reply types (positive, OOO, meeting request, not interested) and suggest Next Moves. The "Did anyone get back to me?" tool. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.
check_inbox accepts 1 parameter: since. 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 check_inbox: 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.
check_inbox 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 check_inbox 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 check_inbox. 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.
check_inbox 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