Missing authorization and the use of insecure default resource initialization allow a remote attacker to self-enroll into the mesh and invoke arbitrary tools across all connected MCP backend nodes. The issue exists in the MCP proxy `HandleStreamPassThrough()` function in `mcp service.go` and the OIDC registration flow via the 'GET /info' and 'POST /register' endpoints in `internal/controlplane/server.go`. Specifically, 'GET /info' publicly discloses OIDC configuration, while 'POST /register' auto-enrolls any valid OIDC token holder without claim filtering or ban checks. Furthermore, the default policy binds `sam:system:authenticated` to wildcard services and targets, enabling an attacker to obtain mesh credentials with full read, write, and execution access on backend services.