infomaniak_set_mailbox_spam_policy
Update mailbox spam movement, smart filtering folders, and admin note. Two-phase commit: returns a current-state diff and confirmation token, then applies only if the policy state has not changed.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-set-mailbox-spam-policy.md
What infomaniak_set_mailbox_spam_policy does on Infomaniak Admin
AI agents use infomaniak_set_mailbox_spam_policy 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.
Why infomaniak_set_mailbox_spam_policy is rated Medium
This tool modifies mailbox settings (spam policy, filtering configuration, notes) but does not delete data or execute arbitrary code. The two-phase commit pattern with state validation indicates changes are intentional and reversible.
From the tool's definition Tool description states it 'Update[s] mailbox spam movement, smart filtering folders, and admin note' — explicit write/modification operations on mailbox configuration. Two-phase commit mechanism confirms reversible mutations (not destructive).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_set_mailbox_spam_policy 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_set_mailbox_spam_policy, this is the rule to start with:
infomaniak_set_mailbox_spam_policy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_set_mailbox_spam_policy call is checked against it from then on.
Questions about infomaniak_set_mailbox_spam_policy
Update mailbox spam movement, smart filtering folders, and admin note. Two-phase commit: returns a current-state diff and confirmation token, then applies only if the policy state has not changed. 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.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_set_mailbox_spam_policy: 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_set_mailbox_spam_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the infomaniak_set_mailbox_spam_policy 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_set_mailbox_spam_policy. 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_set_mailbox_spam_policy 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