infomaniak_get_mail_hosting_full
Full mail hosting detail with diagnostic_dns (MX/SPF/DKIM/DMARC health check), quotas (mailboxes + redirections + per-mailbox disk), admin user, parent kSuite link, FQDN list, and team access flag. Use this for mail-config sanity checks. Manager-private.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-mail-hosting-full.md
What infomaniak_get_mail_hosting_full does on Infomaniak Admin
AI agents call infomaniak_get_mail_hosting_full 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.
Why infomaniak_get_mail_hosting_full is rated Low
The tool performs read-only queries of mail hosting configuration and health metrics. It collects and presents data about DNS records, quotas, users, and access flags without altering any state. The explicit purpose is 'sanity checks' and diagnostic review, which are purely informational. No side effects, mutations, or external operations are triggered.
From the tool's definition Tool retrieves 'full mail hosting detail' including 'diagnostic_dns', 'quotas', 'admin user', 'parent kSuite link', 'FQDN list', and 'team access flag' for inspection and sanity checks. No modification, deletion, or execution verbs present.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_get_mail_hosting_full 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_get_mail_hosting_full, this is the rule to start with:
infomaniak_get_mail_hosting_full 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 Infomaniak Admin, apply this rule, and every infomaniak_get_mail_hosting_full call is checked against it from then on.
Questions about infomaniak_get_mail_hosting_full
Full mail hosting detail with diagnostic_dns (MX/SPF/DKIM/DMARC health check), quotas (mailboxes + redirections + per-mailbox disk), admin user, parent kSuite link, FQDN list, and team access flag. Use this for mail-config sanity checks. Manager-private. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_get_mail_hosting_full: 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.
infomaniak_get_mail_hosting_full 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 infomaniak_get_mail_hosting_full 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 infomaniak_get_mail_hosting_full. 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.
infomaniak_get_mail_hosting_full 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.
More on Infomaniak Admin, and thousands of servers like it.
This server
Across the catalogue