infomaniak_get_user_app_accesses
List app accesses for one account user. Read-only admin inventory for access audit and offboarding planning.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-user-app-accesses.md
What infomaniak_get_user_app_accesses does on Infomaniak Admin
AI agents call infomaniak_get_user_app_accesses 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_user_app_accesses is rated Low
This tool retrieves and queries user application access information without creating, modifying, or deleting data. It is a pure read operation used for administrative visibility and compliance purposes. The 'read-only' descriptor and audit context confirm it poses minimal risk when invoked.
From the tool's definition Tool description explicitly states 'List app accesses' and 'Read-only admin inventory' with purpose limited to 'access audit and offboarding planning' - no data modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_get_user_app_accesses 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_user_app_accesses, this is the rule to start with:
infomaniak_get_user_app_accesses 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_user_app_accesses call is checked against it from then on.
Questions about infomaniak_get_user_app_accesses
List app accesses for one account user. Read-only admin inventory for access audit and offboarding planning. 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_user_app_accesses: 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_user_app_accesses 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_user_app_accesses 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_user_app_accesses. 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_user_app_accesses 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