list_mailboxes
List all mailboxes across accounts with unread counts.
This record as markdown: /tools/io-github-heznpc-iconnect/list-mailboxes.md
What list_mailboxes does on Iconnect
AI agents call list_mailboxes to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_mailboxes is rated Low
This tool queries and returns information about mailboxes and their unread counts. It performs no side effects, creates no new data, modifies nothing, and executes no external operations. It is a straightforward read operation that retrieves existing data from the mail system.
From the tool's definition Tool name 'list_mailboxes' combined with description 'List all mailboxes across accounts with unread counts' indicates retrieval of mailbox metadata without modification.
Attacks that exploit this kind of access
The rule that runs list_mailboxes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_mailboxes, this is the rule to start with:
list_mailboxes 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 Iconnect, apply this rule, and every list_mailboxes call is checked against it from then on.
Questions about list_mailboxes
List all mailboxes across accounts with unread counts. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for list_mailboxes: 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 Iconnect. Nothing to install.
list_mailboxes 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_mailboxes 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_mailboxes. 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_mailboxes is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue