infomaniak_get_database_user
Fetch the detail of a single MariaDB-level user (applications, permissions, link to phpMyAdmin).
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-database-user.md
What infomaniak_get_database_user does on Infomaniak Admin
AI agents call infomaniak_get_database_user 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_database_user is rated Low
This tool retrieves information about a MariaDB user's configuration and permissions. It has no side effects, creates no changes to the system, and merely queries existing data. The phrase 'Fetch the detail' confirms a read-only operation. The blast radius of misuse is minimal—disclosure of user configuration details poses lower risk than write, destructive, or financial operations.
From the tool's definition Tool name contains 'get' and description uses 'Fetch the detail' — retrieving read-only information about a database user's properties and permissions without modification.
Attacks that exploit this kind of access
The rule that runs infomaniak_get_database_user 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_database_user, this is the rule to start with:
infomaniak_get_database_user 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_database_user call is checked against it from then on.
Questions about infomaniak_get_database_user
Fetch the detail of a single MariaDB-level user (applications, permissions, link to phpMyAdmin). 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_database_user: 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_database_user 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_database_user 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_database_user. 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_database_user 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