search_emails

Search emails by subject, sender, recipient, or folder.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 60 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/search-emails.md

WHAT IT DOES

What search_emails does on Starfield

AI agents call search_emails 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
`limit`	number	—	Results per page (default 25)
`query`	string	—
`folder`	string	—	inbox, sent, drafts, trash
`personId`	string	—
`companyId`	string	—

Parameters from the server's own tool schema.

RISK

Why search_emails is rated Low

Even though search_emails 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 signalsAccepts file system path (folder)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_emails 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 search_emails, this is the rule to start with:

search_emails Allowed

search_emails is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_emails": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every search_emails call is checked against it from then on.

FAQ

Questions about search_emails

What does the search_emails tool do? +

Search emails by subject, sender, recipient, or folder. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does search_emails accept? +

search_emails accepts 6 parameters: page, limit, query, folder, personId, companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_emails? +

Register the Starfield MCP server in PolicyLayer and add a rule for search_emails: 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.

What risk level is search_emails? +

search_emails is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_emails? +

Yes. Add a rate_limit block to the search_emails 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.

How do I block search_emails completely? +

Set action: deny in the PolicyLayer policy for search_emails. 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.

What MCP server provides search_emails? +

search_emails 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.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →