# infomaniak_get_mailbox_security

Read mailbox security and spam-control state: authorized senders, blocked senders, spam move policy, mail filtering folders, and note.

Agent View of the PolicyLayer registry record for `infomaniak_get_mailbox_security`. HTML page: https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-mailbox-security

## Facts

- Tool: `infomaniak_get_mailbox_security`
- Server: Infomaniak Admin (`henrikogaard/infomaniak-admin-mcp`) — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp.md
- Homepage: https://github.com/henrikogaard/infomaniak-admin-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "infomaniak_get_mailbox_security",
    "arguments": {}
  }
}
```

## Why infomaniak_get_mailbox_security is rated Low

This tool retrieves configuration and state information about mailbox security settings without any side effects. It is a read-only query operation that does not create, modify, or delete data. The blast radius of misuse is minimal—an agent could only gather information about existing security configurations.

From the tool's own definition: "The tool name explicitly states 'get_mailbox_security' and the description indicates it 'Read[s] mailbox security and spam-control state' with operations limited to retrieving 'authorized senders, blocked senders, spam move policy, mail filtering folders, and…"

## Use case

AI agents call infomaniak_get_mailbox_security 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Infomaniak Admin:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "infomaniak_get_mailbox_security": {}
  }
}
```

## Other tools on Infomaniak Admin (216)

- `infomaniak_cancel_user_pending_invitations` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-cancel-user-pending-invitations.md
- `infomaniak_delete_account_invitation` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-account-invitation.md
- `infomaniak_delete_account_tag` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-account-tag.md
- `infomaniak_delete_account_team` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-account-team.md
- `infomaniak_delete_certificate` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-certificate.md
- `infomaniak_delete_database` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-database.md
- `infomaniak_delete_drive_activity_report` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-drive-activity-report.md
- `infomaniak_delete_drive_user` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-drive-user.md
- `infomaniak_delete_hosting_user` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-hosting-user.md
- `infomaniak_delete_mailbox` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-mailbox.md
- `infomaniak_delete_mailbox_filter` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-mailbox-filter.md
- `infomaniak_delete_mailbox_filter_script` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-mailbox-filter-script.md
- `infomaniak_delete_redirection` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-redirection.md
- `infomaniak_delete_site` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-site.md
- `infomaniak_delete_site_alias` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-site-alias.md
- `infomaniak_dns_delete_record` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-dns-delete-record.md
- `infomaniak_empty_drive_trash` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-empty-drive-trash.md
- `infomaniak_empty_mailbox_trash` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-empty-mailbox-trash.md
- `infomaniak_manage_kchat_channel` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-kchat-channel.md
- `infomaniak_manage_mail_device_access` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-mail-device-access.md
- `infomaniak_manage_public_cloud_kubernetes_service` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-public-cloud-kubernetes-service.md
- `infomaniak_manage_public_cloud_project` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-public-cloud-project.md
- `infomaniak_purge_spam_folder` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-purge-spam-folder.md
- `infomaniak_remove_account_team_users` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-account-team-users.md
- `infomaniak_remove_drive_file_access_team` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-drive-file-access-team.md
- `infomaniak_remove_drive_file_access_user` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-drive-file-access-user.md
- `infomaniak_remove_drive_share_link` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-drive-share-link.md
- `infomaniak_remove_drive_trash_item` — Destructive — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-remove-drive-trash-item.md
- `infomaniak_api_call` — Execute — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-api-call.md
- `infomaniak_lock_drive_user` — Execute — https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp/infomaniak-lock-drive-user.md
- …and 186 more: https://policylayer.com/tools/henrikogaard-infomaniak-admin-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=henrikogaard-infomaniak-admin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/henrikogaard-infomaniak-admin-mcp
