infomaniak_manage_public_cloud_database_service
Manage Public Cloud DBaaS lifecycle and operational actions with two-phase confirmation.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-public-cloud-database-service.md
What infomaniak_manage_public_cloud_database_service does on Infomaniak Admin
AI agents invoke infomaniak_manage_public_cloud_database_service to trigger actions in Infomaniak Admin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why infomaniak_manage_public_cloud_database_service is rated High
Managing a database service lifecycle covers a broad range of operations including starting, stopping, scaling, and potentially destroying database instances. 'Lifecycle and operational actions' implies execution of operations that can affect running services. While the two-phase confirmation adds a safety gate, the underlying actions can be highly impactful (e.g., restarting or reconfiguring a production database).
From the tool's definition Manage Public Cloud DBaaS lifecycle and operational actions with two-phase confirmation
Attacks that exploit this kind of access
The rule that runs infomaniak_manage_public_cloud_database_service 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_manage_public_cloud_database_service, this is the rule to start with:
infomaniak_manage_public_cloud_database_service stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_manage_public_cloud_database_service call is checked against it from then on.
Questions about infomaniak_manage_public_cloud_database_service
Manage Public Cloud DBaaS lifecycle and operational actions with two-phase confirmation. It is categorised as a Execute tool in the Infomaniak Admin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_manage_public_cloud_database_service: 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_manage_public_cloud_database_service is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the infomaniak_manage_public_cloud_database_service 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_manage_public_cloud_database_service. 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_manage_public_cloud_database_service 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.
Across the catalogue