One person, two devices
Tailscale has made OAuth apps generally available and named Grok Bot as a production integration. When a user authorizes the bot, it joins the private Tailscale network as a device associated with that user. Tailscale says it can then reach an internal Model Context Protocol server without the operator opening that server to the public internet. The company’s older OAuth client model provisions devices under a shared service identity.
The scope of consent
A user association answers who authorized an agent. It leaves a second decision for the network owner. An engineer might need a direct database connection from a laptop and want an assistant to query only a designated tool on an internal server. Both devices have a connection to the same engineer. A rule that considers only the user has too little information to express those two assignments.
What an audit entry can establish
Tailscale says its Premium and Enterprise plans expose a device posture attribute for the integration. Its policy example uses that distinction to limit the bot’s reach. Other plans can apply a device tag after authentication and use tag-based rules. In a later review, the record tying the device to the engineer may help explain how access began. Determining what the agent could reach also requires the effective network policy. Neither fact alone establishes who initiated a particular action inside the application.
Sources & further reading
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
