Skip to content

Agent Mesh

docs: the node checks a service name as a service pattern

Tomas Tormob5d9092ad4c5
diff --git a/site/content/docs/guides/exposing-services.md b/site/content/docs/guides/exposing-services.md
index 6425bceb..db82b3e1 100644
--- a/site/content/docs/guides/exposing-services.md
+++ b/site/content/docs/guides/exposing-services.md
@@ -31,8 +31,8 @@ one, so an agent with access to the node cannot make it publish a new
backend. To change the services, edit the file and restart the node. The
[node configuration reference](../../reference/node-config/) lists every key.
-A `name` must be a valid DNS-style label sequence (`db-reader`,
-`build.runner`), because the mesh uses it in URLs and in policy. A policy
+Write a `name` as dot-separated labels of letters, digits, `_` and `-`
+(`db-reader`, `build.runner`), because the mesh uses it in URLs and in policy. A policy
grant refers to the pair `type://name`, so `mcp://calculator` in the policy
means this service and no other.
diff --git a/site/content/docs/reference/node-config.md b/site/content/docs/reference/node-config.md
index 92e69dac..8ce48d24 100644
--- a/site/content/docs/reference/node-config.md
+++ b/site/content/docs/reference/node-config.md
@@ -79,7 +79,7 @@ A list. Each entry has these keys:
| Key | Required | Meaning |
|---|---|---|
| `type` | yes | `mcp`, `inference` or `a2a`. `egress` is refused here: a destination outside the mesh is assigned to nodes by the control plane, in the [egress section](../policy/#egress-destinations) of the mesh policy. |
-| `name` | yes | Unique on this node. DNS-style labels separated by dots (`db-reader`, `build.runner`). Policy grants refer to `type://name`. |
+| `name` | yes | Unique on this node. Dot-separated labels, each 1 to 63 characters of `[a-zA-Z0-9_-]` with no leading `-` (`db-reader`, `build.runner`). The node checks the name as a [service pattern](../policy/#service-patterns), so a wildcard form or a `/path` suffix passes too. Policy grants refer to `type://name`. |
| `description` | no | Shown in discovery results and in the console. |
| `target_url` | `mcp`: this or `command`; `inference` and `a2a`: yes | Backend URL that the node proxies to. Embedded credentials (`http://user:pass@`) are refused. |
| `command` | `mcp` only: this or `target_url` | Argument vector of a subprocess that speaks MCP over stdio. The node starts and supervises it. |