infomaniak_audit_account_access
Read-only admin audit of account users and their app accesses. Highlights privileged access, broad access, and per-user fetch errors.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-audit-account-access.md
What infomaniak_audit_account_access does on Infomaniak Admin
AI agents call infomaniak_audit_account_access 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_audit_account_access is rated Low
This tool retrieves and queries audit data about user access patterns and privileges without any ability to modify, delete, or execute actions. It is purely informational.
From the tool's definition Tool name contains 'audit' and description explicitly states 'Read-only admin audit' with functions limited to querying 'account users and their app accesses' with no modification, deletion, or execution capabilities.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_audit_account_access 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_audit_account_access, this is the rule to start with:
infomaniak_audit_account_access 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_audit_account_access call is checked against it from then on.
Questions about infomaniak_audit_account_access
Read-only admin audit of account users and their app accesses. Highlights privileged access, broad access, and per-user fetch errors. 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_audit_account_access: 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_audit_account_access 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_audit_account_access 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_audit_account_access. 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_audit_account_access 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