Connect Sanity to Glean
Give Glean governed access to Sanity’s 55 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Sanity to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Add Sanity to Runlayer
Sanity isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Sanity’s 55 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Sanity
Sign in the way Sanity requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Sanity from Glean
Sanity’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
55 Sanity tools in Glean
Runlayer policy decides which of these Glean users can call.
Get UI context
Returns UI enrichment data for widgets.
Add cors origin
Adds CORS origin(s) to allow client-side requests to a Sanity project
Assets upload status
Retrieve the status and result of your asset upload by operationId.
Delete cors origins
Deletes a CORS origin from a Sanity project
List cors origins
Lists all CORS origins configured for a Sanity project
Create dataset
Creates a new dataset with specified name and access settings
Create documents
Create one or more draft documents by directly providing structured content.
Create project
Creates a new Sanity project and initializes it with a dataset and API tokens
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Sanity call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more