infomaniak_rotate_mail_dkim
Check or rotate the DKIM key for a mail hosting. The check path is read-only; rotate uses two-phase confirmation.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-rotate-mail-dkim.md
What infomaniak_rotate_mail_dkim does on Infomaniak Admin
AI agents use infomaniak_rotate_mail_dkim 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_rotate_mail_dkim is rated Medium
Rotating a DKIM key modifies the cryptographic signing configuration for mail hosting. While it uses a two-phase confirmation (suggesting reversibility in process), the actual rotation changes the DKIM key, which affects email authentication and deliverability. This is a Write operation with high severity since misuse could break email signing for an entire mail hosting domain, causing deliverability failures.
From the tool's definition rotate the DKIM key for a mail hosting. The check path is read-only; rotate uses two-phase confirmation.
Attacks that exploit this kind of access
The rule that runs infomaniak_rotate_mail_dkim 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_rotate_mail_dkim, this is the rule to start with:
infomaniak_rotate_mail_dkim 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_rotate_mail_dkim call is checked against it from then on.
Questions about infomaniak_rotate_mail_dkim
Check or rotate the DKIM key for a mail hosting. The check path is read-only; rotate uses two-phase confirmation. 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_rotate_mail_dkim: 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_rotate_mail_dkim 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_rotate_mail_dkim 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_rotate_mail_dkim. 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_rotate_mail_dkim 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