infomaniak_delete_mailbox_filter
Delete a mailbox Sieve filter by name. Two-phase commit with current filter inventory guard before DELETE.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-mailbox-filter.md
What infomaniak_delete_mailbox_filter does on Infomaniak Admin
AI agents call infomaniak_delete_mailbox_filter to permanently remove resources in Infomaniak Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why infomaniak_delete_mailbox_filter is rated Critical
The tool irreversibly deletes email filtering rules via explicit DELETE operation. While mitigated by two-phase commit safeguards, mailbox filters control email routing and organization—deletion cannot be undone and impacts email functionality. This qualifies as Destructive rather than Execute because the action is fundamentally about removing data/configuration.
From the tool's definition Delete a mailbox Sieve filter by name. Two-phase commit with current filter inventory guard before DELETE.
Attacks that exploit this kind of access
The rule that runs infomaniak_delete_mailbox_filter 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_delete_mailbox_filter, this is the rule to start with:
infomaniak_delete_mailbox_filter is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_delete_mailbox_filter call is checked against it from then on.
Questions about infomaniak_delete_mailbox_filter
Delete a mailbox Sieve filter by name. Two-phase commit with current filter inventory guard before DELETE. It is categorised as a Destructive tool in the Infomaniak Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_delete_mailbox_filter: 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_delete_mailbox_filter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the infomaniak_delete_mailbox_filter 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_delete_mailbox_filter. 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_delete_mailbox_filter 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.
Across the catalogue