Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: name the granted_service_set facts that exact entries compile to
Tomas Tormo3ef2861e9e3c
diff --git a/site/content/docs/concepts/authorization.md b/site/content/docs/concepts/authorization.mdindex 1de2d3d1..0042faf8 100644--- a/site/content/docs/concepts/authorization.md+++ b/site/content/docs/concepts/authorization.md@@ -117,14 +117,14 @@ control plane resolves the identity's roles from the bindings and writes theresult into the credential's authority block as Datalog facts: one `role(...)`fact per role, plus the grants compiled from the lists of every role. Forexample, `allowed_services: ["mcp://calculator"]` becomes-`granted_service_exact("mcp", "calculator")`, `mcp://*` becomes+`granted_service_set("mcp", ["calculator"])`, `mcp://*` becomes`granted_service_all("mcp")`, and `mcp://*.internal` becomes`granted_service_suffix("mcp", ".internal")`. Wildcards keep their dot, so`*.acme.example` matches `svc.acme.example` but not `evil-acme.example`.The control plane also renders the policy as Datalog rules such as`role("developer") <- group("eng")` and-`granted_service_exact("mcp", "calculator") <- role("developer")`. Nodes+`granted_service_set("mcp", ["calculator"]) <- role("developer")`. Nodesfetch this text every `--control-plane-sync-interval` (15 minutes by default,sooner when a policy update event reaches them) and add it to theirauthorizer as it arrives. When a node verifies a credential, these rules rundiff --git a/site/content/docs/reference/policy.md b/site/content/docs/reference/policy.mdindex 12b5f8b4..3565fb52 100644--- a/site/content/docs/reference/policy.md+++ b/site/content/docs/reference/policy.md@@ -84,7 +84,7 @@ rejected, because the path belongs in the role's `http` entry or a| Pattern | Compiles to | Matches ||---|---|---|-| `mcp://calculator` | `granted_service_exact("mcp", "calculator")`. Several exact entries of one type are merged into one `granted_service_set`. | that service |+| `mcp://calculator` | `granted_service_set("mcp", ["calculator"])`. All exact entries of one type share one `granted_service_set` fact. | that service || `mcp://*.internal` | `granted_service_suffix("mcp", ".internal")` | `a.internal` and `b.c.internal`, but not `xinternal` || `mcp://build.*` | `granted_service_prefix("mcp", "build.")` | `build.runner`, but not `builder` || `mcp://*` | `granted_service_all("mcp")` | every MCP service |@@ -100,7 +100,7 @@ runs. A role that should be able to list the tools of a node needs it.### Publishing`allowed_publish` takes the same patterns and compiles them to-`granted_publish_*` facts: `granted_publish_exact("mcp", "calculator")`,+`granted_publish_*` facts: `granted_publish_set("mcp", ["calculator"])`,`granted_publish_all("mcp")`, `granted_publish_all_types(true)` and so on.They say what a member may serve, where `allowed_services` says what it maycall, and the two are independent: a role that may call `mcp://calc` may@@ -118,7 +118,7 @@ SDKs make the check; a member's own record under its peer ID, and a node'scatalog (`system://mesh.catalog`), name no service and need no grant.An egress destination needs no entry: `served_by` selects the nodes that-serve it, and the control plane mints `granted_publish_exact("egress", "<name>")`+serve it, and the control plane mints `granted_publish_set("egress", ["<name>"])`into their credentials with the destination.A change to `allowed_publish` takes effect without a new credential. The