infomaniak_manage_public_cloud_kubernetes_service
Create, update, or delete a Public Cloud Kubernetes service with two-phase confirmation.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-manage-public-cloud-kubernetes-service.md
What infomaniak_manage_public_cloud_kubernetes_service does on Infomaniak Admin
AI agents call infomaniak_manage_public_cloud_kubernetes_service 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.
Why infomaniak_manage_public_cloud_kubernetes_service is rated Critical
The tool explicitly includes 'delete' as one of its operations on a Kubernetes service, which is irreversible and represents the most severe applicable category. Deleting a Kubernetes cluster can destroy all workloads, configurations, and persistent data associated with it, making this a critical-severity destructive action.
From the tool's definition Create, update, or delete a Public Cloud Kubernetes service
Attacks that exploit this kind of access
The rule that runs infomaniak_manage_public_cloud_kubernetes_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_kubernetes_service, this is the rule to start with:
infomaniak_manage_public_cloud_kubernetes_service is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_manage_public_cloud_kubernetes_service call is checked against it from then on.
Questions about infomaniak_manage_public_cloud_kubernetes_service
Create, update, or delete a Public Cloud Kubernetes service with two-phase confirmation. 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.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_manage_public_cloud_kubernetes_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_kubernetes_service is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the infomaniak_manage_public_cloud_kubernetes_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_kubernetes_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_kubernetes_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