infomaniak_delete_database

Delete a MariaDB database. Two-phase commit, manager-private API. WARNING: the database content (tables, rows) is wiped and cannot be recovered without an Infomaniak backup.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-delete-database.md

WHAT IT DOES

What infomaniak_delete_database does on Infomaniak Admin

AI agents call infomaniak_delete_database to permanently remove resources in Infomaniak Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why infomaniak_delete_database is rated Critical

This tool irreversibly deletes an entire database and its contents with no undo capability. The explicit warning that data 'cannot be recovered' (except via external backups) confirms this is a destructive operation. Despite the two-phase commit safeguard, the underlying action is permanently data-destructive, making it critical severity due to the potential for large-scale data loss if invoked inappropriately.

From the tool's definition Delete a MariaDB database... the database content (tables, rows) is wiped and cannot be recovered without an Infomaniak backup.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_delete_database 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_delete_database, this is the rule to start with:

infomaniak_delete_database Hidden

infomaniak_delete_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "infomaniak_delete_database"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_delete_database call is checked against it from then on.

FAQ

Questions about infomaniak_delete_database

What does the infomaniak_delete_database tool do? +

Delete a MariaDB database. Two-phase commit, manager-private API. WARNING: the database content (tables, rows) is wiped and cannot be recovered without an Infomaniak backup. It is categorised as a Destructive tool in the Infomaniak Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on infomaniak_delete_database? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_delete_database: 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.

What risk level is infomaniak_delete_database? +

infomaniak_delete_database is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit infomaniak_delete_database? +

Yes. Add a rate_limit block to the infomaniak_delete_database 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.

How do I block infomaniak_delete_database completely? +

Set action: deny in the PolicyLayer policy for infomaniak_delete_database. 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.

What MCP server provides infomaniak_delete_database? +

infomaniak_delete_database 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.

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_database on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →