Runlayer Plugin
Unified endpoint
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Runlayer for Glean
Give Glean approved MCP tools through Runlayer’s remote endpoints.
01
Connect
Give everyone in Glean the golden path to approved tools
Add one Runlayer Plugin endpoint so people find every tool they’re approved for, or connect a single server when you want a narrower set.
Direct connection
Per-connector endpoint
Give the client a dedicated Runlayer URL for one connector. Identity, policy, scanning, and audit still stay attached to every request.
Connection support
Remote MCP
02
Observe
See how Glean is being used
Runlayer uses every channel Glean exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.
OTLP telemetry
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Read the guide03
Enforce
Know exactly what Glean can block
Each row reflects Runlayer’s enforcement code for Glean: what it can stop before a call runs, block afterward, or redact in place.
| Control | Support | What that means |
|---|---|---|
| Pre-tool deny | At the gateway | Runlayer has no hook in Glean that can stop a tool call; Runlayer policies stop calls to Runlayer connectors at the gateway. |
| Post-tool output block | At the gateway | Runlayer has no hook in Glean that can block tool output; ToolGuard blocks unsafe output from Runlayer connectors at the gateway. |
| Output rewrite | At the gateway | Runlayer has no hook in Glean that can rewrite tool output; ToolGuard masks sensitive output from Runlayer connectors at the gateway. |
Enforcement postureNot applicable
Minimum supported versionNo minimum listed
Client-specific caveats
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
MCP servers
Connect Glean to the tools your teams use
Setup steps, tools, and controls for each MCP server in Glean.
