Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
clarify policies
Antonio Ojea0cb25bb15dcb
diff --git a/site/content/docs/development/policy.md b/site/content/docs/development/policy.mdindex b009f961..9e601aae 100644--- a/site/content/docs/development/policy.md+++ b/site/content/docs/development/policy.md@@ -72,7 +72,8 @@ Admins define central permissions by mapping OIDC roles to specific capabilities* **Default Namespace (`system`)**: If a service string does not contain a `:` separator (e.g., `my-tool`), it automatically defaults to the `system` type (parsed as `system:my-tool`).* **Wildcards**: Because `allowed_services` translates to the two-argument Biscuit fact `service($type, $name)`, SAM natively supports wildcards. You can grant access to an entire type via `type:*` (e.g., `mcp:*`), or grant global access to everything via `*`.* **MCP Namespace Convention**: The `mcp:` prefix (`api.MCPServicePrefix`) is the explicit convention for all Model Context Protocol targets. When remote nodes query local nodes for tool catalogs, if the local service is an MCP server and is missing the `mcp:` prefix in its name, the proxy layer will automatically prepend `mcp:` prior to enforcing the authorization policy to prevent it from accidentally falling back into the `system:` namespace.-+ * **Custom Namespaces & Authorization Boundaries**: The system allows arbitrary prefixes (e.g., `plugin:my-tool`). The string is strictly split at the *first* colon. The left side (`plugin`) becomes the namespace used exclusively for Biscuit authorization checks (`service("plugin", "my-tool")`). If an administrator registers a service as `system:my-tool`, they are intentionally placing it behind the strict `system` authorization policy. Users cannot bypass security by adding prefixes—they only restrict access further.+ * **Service Routing Fallback**: When authorizing a connection, the node first looks up the stripped target name (`my-tool`). If it fails, it explicitly falls back to the full original target string (`system:my-tool`). This allows users to register custom namespaced tools (e.g., `Name: "plugin:linter"`) and route to them securely while still strictly enforcing the `plugin` authorization policy.> [!NOTE]> The `*` global wildcard is a special case. It maps exactly to type `*` and name `*`. It does *not* default to the `system` type.