infomaniak_get_my_profile
Get the identity of the currently-authenticated Infomaniak user: name, email, language, country, timezone, current_account_id (= the organization being managed by default), and the full security posture (2FA status, recovery email, validated phone, trusted devices, last login). Use this first to ...
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-my-profile.md
What infomaniak_get_my_profile does on Infomaniak Admin
AI agents call infomaniak_get_my_profile to retrieve information from Infomaniak Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why infomaniak_get_my_profile is rated Low
This tool queries and retrieves user profile information and security status without creating, modifying, deleting, or executing any operations. It is purely informational—returning metadata about the authenticated user. The recommendation to 'use this first to confirm which user + account the MCP is acting on behalf of' further confirms it is a read/query operation.
From the tool's definition Tool description states 'Get the identity...name, email, language, country, timezone' and 'retrieve...2FA status, recovery email, validated phone, trusted devices, last login'.
Attacks that exploit this kind of access
The rule that runs infomaniak_get_my_profile 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_get_my_profile, this is the rule to start with:
infomaniak_get_my_profile is read-only, so it stays allowed. 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_get_my_profile call is checked against it from then on.
Questions about infomaniak_get_my_profile
Get the identity of the currently-authenticated Infomaniak user: name, email, language, country, timezone, current_account_id (= the organization being managed by default), and the full security posture (2FA status, recovery email, validated phone, trusted devices, last login). Use this first to confirm which user + account the MCP is acting on behalf of. Manager-private — requires SASESSION cookie. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_get_my_profile: 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_get_my_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the infomaniak_get_my_profile 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_get_my_profile. 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_get_my_profile 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