infomaniak_list_mailboxes

List every mailbox on a given mail hosting.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-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/henrikogaard-infomaniak-admin-mcp/infomaniak-list-mailboxes.md

WHAT IT DOES

What infomaniak_list_mailboxes does on Infomaniak Admin

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

RISK

Why infomaniak_list_mailboxes is rated Low

This tool retrieves and enumerates mailbox information without creating, modifying, deleting, or executing any operations. It is purely informational and poses minimal risk even if misused by an agent, as it only exposes read access to existing mailbox metadata.

From the tool's definition Tool name 'list_mailboxes' and description 'List every mailbox on a given mail hosting' indicate a query/retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_list_mailboxes safely

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

infomaniak_list_mailboxes Allowed

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

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

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

FAQ

Questions about infomaniak_list_mailboxes

What does the infomaniak_list_mailboxes tool do? +

List every mailbox on a given mail hosting. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on infomaniak_list_mailboxes? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_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 Infomaniak Admin. Nothing to install.

What risk level is infomaniak_list_mailboxes? +

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

Can I rate-limit infomaniak_list_mailboxes? +

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

How do I block infomaniak_list_mailboxes completely? +

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

What MCP server provides infomaniak_list_mailboxes? +

infomaniak_list_mailboxes is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools →

Across the catalogue

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

Guides

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