list_email_accounts

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/list-email-accounts.md

WHAT IT DOES

What list_email_accounts does on Local

AI agents call list_email_accounts to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_email_accounts is rated Low

This tool retrieves account metadata from Mail.app without side effects. It is purely informational, enabling enumeration of available accounts to support subsequent read operations. No data is created, modified, deleted, or executed; it is a simple query operation.

From the tool's definition Tool description explicitly states 'Lists all Mail.app accounts by name' with no modification or deletion capability. The tool is a discovery/query operation used to 'fetch messages' in a read-only manner.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_email_accounts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_email_accounts, this is the rule to start with:

list_email_accounts Allowed

list_email_accounts 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": {
    "list_email_accounts": {}
  }
}

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

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

FAQ

Questions about list_email_accounts

What does the list_email_accounts tool do? +

Lists all Mail.app accounts by name. Call this first to discover account names, then use list_emails(account=name) to fetch messages from a specific account. Much faster than querying all accounts at once. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_email_accounts? +

Register the Local MCP server in PolicyLayer and add a rule for list_email_accounts: 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 Local. Nothing to install.

What risk level is list_email_accounts? +

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

Can I rate-limit list_email_accounts? +

Yes. Add a rate_limit block to the list_email_accounts 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 list_email_accounts completely? +

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

list_email_accounts is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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