This record as markdown: /tools/com-local-mcp-local-mcp/list-accounts.md
What list_accounts does on Local
AI agents call list_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.
Why list_accounts is rated Low
This tool performs a read-only query of configured email accounts. It retrieves information without creating, modifying, or deleting any data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent could enumerate email accounts but cannot alter them or access private data beyond account metadata. Classification as Read is appropriate.
From the tool's definition Tool name 'list_accounts' combined with description 'Lists email accounts configured in Mail.app' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_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_accounts, this is the rule to start with:
list_accounts 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 Local, apply this rule, and every list_accounts call is checked against it from then on.
Questions about list_accounts
Lists email accounts configured in Mail.app. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for list_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.
list_accounts 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_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
More on Local, and thousands of servers like it.
This server
Across the catalogue