infomaniak_manage_mailbox_filter_lifecycle

Enable/disable mailbox filters or Sieve scripts, or reorder filters. All changes use two-phase confirmation with a fresh filter snapshot.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-mailbox-filter-lifecycle.md

WHAT IT DOES

What infomaniak_manage_mailbox_filter_lifecycle does on Infomaniak Admin

AI agents use infomaniak_manage_mailbox_filter_lifecycle to create or update resources in Infomaniak Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infomaniak Admin environment.

RISK

Why infomaniak_manage_mailbox_filter_lifecycle is rated Medium

The tool creates or modifies email filter configurations (enabling, disabling, reordering), which constitutes Write-class behavior. Severity is high because misconfigured mailbox filters could cause email delivery failures, loss of email visibility, or unintended email routing affecting business communications.

From the tool's definition Tool enables modification of mailbox filters and Sieve scripts: 'Enable/disable mailbox filters or Sieve scripts, or reorder filters.' These are reversible configuration changes that alter email processing behavior.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_manage_mailbox_filter_lifecycle 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_manage_mailbox_filter_lifecycle, this is the rule to start with:

infomaniak_manage_mailbox_filter_lifecycle Rate-limited

infomaniak_manage_mailbox_filter_lifecycle stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infomaniak_manage_mailbox_filter_lifecycle": {
      "limits": [
        {
          "counter": "infomaniak_manage_mailbox_filter_lifecycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_manage_mailbox_filter_lifecycle call is checked against it from then on.

FAQ

Questions about infomaniak_manage_mailbox_filter_lifecycle

What does the infomaniak_manage_mailbox_filter_lifecycle tool do? +

Enable/disable mailbox filters or Sieve scripts, or reorder filters. All changes use two-phase confirmation with a fresh filter snapshot. It is categorised as a Write tool in the Infomaniak Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on infomaniak_manage_mailbox_filter_lifecycle? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_manage_mailbox_filter_lifecycle: 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_manage_mailbox_filter_lifecycle? +

infomaniak_manage_mailbox_filter_lifecycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit infomaniak_manage_mailbox_filter_lifecycle? +

Yes. Add a rate_limit block to the infomaniak_manage_mailbox_filter_lifecycle 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_manage_mailbox_filter_lifecycle completely? +

Set action: deny in the PolicyLayer policy for infomaniak_manage_mailbox_filter_lifecycle. 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_manage_mailbox_filter_lifecycle? +

infomaniak_manage_mailbox_filter_lifecycle 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →