chore: Dial admin updates (#463)

Author: sr-remsha

docs/tutorials/3.admin/access-management-keys.md

@@ -100,6 +100,7 @@ In the Properties tab, you can view metadata and manage the selected settings fo
 | **Key value** | Yes | Secret string used for authentication.<br />Initially hidden - click **👁️** to reveal.<br />Press **Copy** to copy it to clipboard. |
 | **Secured** | Yes | Indication if it is [secured API key](/docs/platform/3.core/4.privacy.md#applications-audit-logs). |
 | **Topics** | No | Tags assigned to the key (e.g. "admin", "user"). |
+| **IPs access restriction** | No | A list of IP address ranges. <br />- **Allow all** or undefined: Any client can have access.<br />- **Block all**: Access is prohibited to all clients. <br />- **Only selected ranges**: Only clients with IP address within the given ranges may have access. IP address could be IPv4 or IPv6. |
 
 ![](img/keys-properties.png)
 

docs/tutorials/3.admin/assets-toolsets.md

@@ -161,7 +161,7 @@ Having selected and configured any authentication method, click **Save** and **L
 
 [Tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools) are specific functions supported by a related MCP server that can be used by clients to perform specific actions. On this screen, you can find and manage all tools supported by the related MCP server.
 
-In case your toolset was created based on the MCP container deployed in DIAL, the content of this screen is inherited from the related [MCP container](/docs/tutorials/3.admin/deployments-mcp.md#tools-overview).
+In case your toolset was created based on the MCP container deployed in DIAL, the content of this screen is inherited from the related [MCP container](/docs/tutorials/3.admin/deployments-mcp.md#tools-overview) and displays all the **enabled** tools. Click [Manage tools](#manage-tools) to access, try and enable all the available tools.
 
 #### Use all tools
 

docs/tutorials/3.admin/deployments-images.md

@@ -17,12 +17,13 @@ On the main screen, you can see all the available and add new images for MCP Ser
 | ID | Unique identifier of the image. |
 | Version | Version of the image. |
 | Name | Name of the image. |
+| Author | Deployment author email address. |
 | Description | Brief description of the image. |
 | Type | Type of the image (MCP or Interceptor). |
 | Source | Image or a Source code. |
 | Status | Current status of the image. |
-| Update time | Date and time when the image was last updated. |
-| Create time | Date and time when the image was created. |
+| Updated time | Date and time when the image was last updated. |
+| Creation time | Date and time when the image was created. |
 | Topics | List of topics associated with the image. |
 | Transport type | Transport type used by the MCP image:<br />- **Remote** (HTTP/SSE)<br />- **Local** (STDIO). |
 | Actions | Buttons to manage the selected image:<br/>- **Delete**: Use to remove the image.<br/>- **Duplicate**: Use to create a copy of the image.<br/>- **Open in a new tab**: Use to open image properties in a new tab in your browser. |
@@ -52,7 +53,7 @@ On the main screen, you can add new images for MCP Servers and Interceptors.
 
 Global firewall settings define an allow list of authorized domain names for all image builds in the environment. This helps operators avoid duplicating common allowed domains across images. [Individual image allow lists](#firewall-settings) can extend the global list.
 
-**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters.
+**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. Domain name must not include leading or trailing hyphens in labels.
 
 ![ ](img/images_global_firewall.png)
 
@@ -87,13 +88,13 @@ In the Properties tab, you can preview and modify selected image's basic propert
 | Updated Time | - | No | Date and time when the image was last updated. |
 | Source type | - | No | Source type of the Docker image:<br />- **Docker Image**<br />- **Source Code** |
 | Status | - | No | Current status of the image. |
-| Name | Yes | Yes | Name of the image. |
+| Name | Yes | Yes | Name of the image. <br /> Must be between 2 and 255 characters long. <br /> Can contain only letters, numbers, spaces, underscores, and hyphens. <br /> Special characters are not allowed. |
 | Description | No | Yes | Brief description of the image. |
-| Maintainer | No | Yes | The maintainer of the image. |
-| Topics | No | Yes | List of topics associated with the image. |
+| Maintainer | No | Yes | Email address of the maintainer of the image. |
+| Topics | No | Yes | List of topics associated with the image. Click to display a list of available topics. <br />You can add your own custom topics to the list following these rules:<br /> - The topic name must not exceed 255 characters. <br /> - The topic name must not contain leading or trailing spaces.|
 | Source type | Conditional | Yes | **Note**: Required for MCP type of image.<br />The source type of the Docker image:<br />- **Docker Image**<br />- **Source Code** |
-| Docker image URI | Conditional | Yes | URI of the Docker image.<br/>Applies to both MCP (if Source type = Docker image) and Interceptor types. |
-| Source code repository parameters | Conditional | Yes | Applies if Type = MCP Image and Source type = Source code .<br/>- **Repo URL** (required): a source code repository URL.<br />- **Branch name**: the name of the branch in the source code repository.<br />- **SHA**: the SHA in the source code repository.<br />- **Base directory**: the directory path with the Docker file. |
+| Docker image URI | Conditional | Yes |  Valid Docker image URI (validated on backend). If provided, must not start or end with `/`.<br/>Applies to both MCP (if Source type = Docker image) and Interceptor types. |
+| Source code repository parameters | Conditional | Yes | Applies if Type = MCP Image and Source type = Source code .<br/>- **Repo URL** (required): Source code repository URL. If provided, must not start or end with `/`.<br />- **Branch name**: the name of the branch in the source code repository.<br />- **SHA**: the SHA in the source code repository.<br />- **Base directory**: The directory path with the Docker file. If provided, must not start or end with `/`. |
 | MCP transport type | Conditional | Yes | Applies only to MCP type of image.<br/>The transport type used by the MCP image:<br />- **Remote** (HTTP/SSE)<br />- **Local** (STDIO). |
 
 ![ ](img/image_properties.png)
@@ -110,7 +111,7 @@ The allow list domains setting specifies which external resources the image buil
 
 > **Note**: These firewall rules do not affect containers that are later created from the image. Containers can have their own firewall settings.
 
-**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters.
+**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. Domain name must not include leading or trailing hyphens in labels.
 
 ![ ](img/image-firewall.png)
 

docs/tutorials/3.admin/deployments-interceptors.md

@@ -89,19 +89,19 @@ In the Properties tab, you can view and edit the selected interceptor container
 
 | Property | Required | Editable | Description |
 |----------|----------|----------|-------------|
-| ID | - | No | Unique identifier for the interceptor container. |
+| ID | - | No | Unique identifier for the interceptor container. Must be between 2 and 36 characters long. Can contain only lowercase Latin letters, numbers, and hyphens. |
 | Interceptor Image | - | No | Docker image from which the interceptor container was created. |
 | Creation Time | - | No | Date and time when the interceptor container was created. |
 | Updated Time | - | No | Date and time when the interceptor container was last updated. |
 | Status | - | No | Current status of the interceptor container (e.g., Running, Stopped). |
 | URL | - | No | URL to access the running interceptor container. |
 | Restarts | - | No | Restart counter for launching containers. Use to identify crash loops. You can find details in the [Execution Log](#execution-log).|
-| Display Name | Yes | Yes | Name of the interceptor container rendered in UI. |
+| Display Name | Yes | Yes | Name of the interceptor container rendered in UI. Must be between 2 and 255 characters long. |
 | Description | No | Yes | Brief description of the interceptor container. |
 | Maintainer | No | Yes | Maintainer of the interceptor container. |
 | Endpoint Configuration | No | Yes | Configuration details for the endpoints exposed by the interceptor container. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
-| Environment Variables | No | Yes | Environment variables set for the interceptor container. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
-| Resources | No | Yes | Resource limits and requests for the interceptor container. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
+| Environment Variables | No | Yes | Environment variables set for the interceptor container. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. <br /> - **Name**: Must be between 1 and 253 characters long. Can contain only letters, numbers, dots `(.)`, hyphens `(-)`, and underscores `(_)`.<br /> - **Value**: Must be between 1 and 253 characters long. Can contain only letters, numbers, dots `(.)`, hyphens `(-)`, and underscores `(_)`. |
+| Resources | No | Yes | Resource limits and requests for the interceptor container. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode.<br />Validation rules: <br /> - Values must be numeric and greater than 0.<br /> - Maximum allowed values for `cpu`, `memory`, and `nvidia.com/gpu` are defined on the backend via environment variables.<br /> - For each matching resource key (e.g. `cpu`), the value in limits must not be less than the value in `requests`. |
 
 ![](img/interceptor_container_properties.png)
 
@@ -113,7 +113,7 @@ In the Properties tab, you can view and edit the selected interceptor container
 
 The whitelist domains setting specifies which external domains the interceptor container is allowed to connect to. This setting controls outgoing traffic from the container, ensuring that it can only communicate with trusted domains (for example, your company’s website or specific client applications).
 
-**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters.
+**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. Domain name must not include leading or trailing hyphens in labels.
 
 ![ ](img/interceptor_container_firewall.png)
 

docs/tutorials/3.admin/deployments-mcp.md

@@ -107,19 +107,19 @@ In the Properties tab, you can preview and modify selected container's basic pro
 
 | Property | Required | Editable | Description |
 |----------|----------|----------|-------------|
-| ID | - | No | Unique identifier of the MCP container. |
+| ID | - | No | Unique identifier of the MCP container. Must be between 2 and 36 characters long. Can contain only lowercase Latin letters, numbers, and hyphens. |
 | MCP Image | - | No | Image from which the MCP container was created. Click to open details or navigate to [MCP Images](/docs/tutorials/3.admin/deployments-images.md). |
 | Creation Time | - | No | Date and time when the MCP container was created. |
 | Updated Time | - | No | Date and time when the MCP container was last updated. |
 | Status | - | No | Current status of the MCP container (e.g., Running, Stopped). |
 | URL | - | No | The URL to access the running MCP container. |
 | Restarts | - | No | Restart counter for launching containers. Use to identify crash loops. You can find details in the [Execution Log](#execution-log). |
-| Display Name | Yes | Yes | Display name of the MCP container rendered in UI. |
+| Display Name | Yes | Yes | Display name of the MCP container rendered in UI. Must be between 2 and 255 characters long. |
 | Description | No | Yes | Brief description of the MCP container. |
 | Maintainer | No | Yes | Maintainer of the MCP container. |
-| Endpoint Configuration | No | Yes | Endpoint configuration of the MCP container:<br /> **Transport**: the transport protocol (HTTP (default) or SSE).<br />**Container endpoint path**: the specific endpoint path where the MCP service is accessible.<br />**Port**: the network port the container uses. <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
-| Environment Variables | No | Yes | List of environment variables for the MCP container. <br />You can add, edit, or remove variables as needed.  <br />**Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
-| Resources | No | Yes | Resource limits for the MCP container, including CPU and memory allocation. You can adjust these settings based on your requirements.<br />**Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
+| Endpoint Configuration | No | Yes | Endpoint configuration of the MCP container:<br /> **Transport**: the transport protocol (HTTP (default) or SSE).<br />**Container endpoint path**: the specific endpoint path where the MCP service is accessible.<br />**Port**: the network port the container uses (If provided, must be between 1 and 65535.). <br /> **Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. |
+| Environment Variables | No | Yes | List of environment variables for the MCP container. <br />You can add, edit, or remove variables as needed.  <br />**Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode. <br /> - **Name**: Must be between 1 and 253 characters long. Can contain only letters, numbers, dots `(.)`, hyphens `(-)`, and underscores `(_)`.<br /> - **Value**: Must be between 1 and 253 characters long. Can contain only letters, numbers, dots `(.)`, hyphens `(-)`, and underscores `(_)`. |
+| Resources | No | Yes | Resource limits for the MCP container, including CPU and memory allocation. You can adjust these settings based on your requirements.<br />**Note**: Changes to these settings can be applied to a running container. Saving changes will trigger a restart in RollingUpdate mode.<br />Validation rules: <br /> - Values must be numeric and greater than 0.<br /> - Maximum allowed values for `cpu`, `memory`, and `nvidia.com/gpu` are defined on the backend via environment variables.<br /> - For each matching resource key (e.g. `cpu`), the value in limits must not be less than the value in `requests`. |
 
 ![](img/mcp_container_properties.png)
 
@@ -131,7 +131,7 @@ In the Properties tab, you can preview and modify selected container's basic pro
 
 The whitelist domains setting specifies which external domains the MCP container is allowed to connect to. This setting controls outgoing traffic from the container, ensuring that it can only communicate with trusted domains (for example, your company’s website or specific client applications).
 
-**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters.
+**Domain name requirements**: Enter the domain name without protocol, e.g., github.com. Each domain must have at least one dot, labels can include letters, numbers, and hyphens (1–63 chars, not starting or ending with a hyphen), and the top-level domain must be at least 2 letters. Domain name must not include leading or trailing hyphens in labels.
 
 ![ ](img/mcp-firewall.png)