infomaniak_purge_spam_folder
Delete all messages currently in a mailbox spam folder. Destructive two-phase commit with mailbox security state guard.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-purge-spam-folder.md
What infomaniak_purge_spam_folder does on Infomaniak Admin
AI agents call infomaniak_purge_spam_folder 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_purge_spam_folder is rated Critical
Purging a spam folder deletes email messages without recovery. While the two-phase commit mitigates accidental invocation, the action itself is irreversible and destroys user data. This is clearly Destructive rather than Write (which is reversible).
From the tool's definition Tool name explicitly states 'purge' (delete permanently); description confirms 'Delete all messages' and 'Destructive two-phase commit'. Purge is irreversible data destruction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs infomaniak_purge_spam_folder 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_purge_spam_folder, this is the rule to start with:
infomaniak_purge_spam_folder 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_purge_spam_folder call is checked against it from then on.
Questions about infomaniak_purge_spam_folder
Delete all messages currently in a mailbox spam folder. Destructive two-phase commit with mailbox security state guard. 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_purge_spam_folder: 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_purge_spam_folder 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_purge_spam_folder 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_purge_spam_folder. 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_purge_spam_folder 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