Connect Glean to Cursor
Give Cursor governed access to Glean’s 16 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Glean to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve Glean in Runlayer
Add Glean from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cursor to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Glean’s 16 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to Glean
Sign in the way Glean requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Glean from Cursor
Glean’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
16 Glean tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Brave actions web search
Searches the web for up-to-date external information from the web.
Chat
AI-powered tool for company knowledge.
Code search
Searches company code and configuration (top matches only).
Create image
Generate a new image from a natural-language prompt using Glean's image generation models, save it as an IMAGE artifact in the user's Library, and return links to view or download it.
Edit image
Modify an existing IMAGE artifact using a natural-language instruction.
Employee search
Finds company employees and their information.
Gmail search
Searches Gmail inbox (Google Workspace) for emails, conversations, and attachments.
Meeting lookup
Searches company calendar meetings and extracts transcripts.
Control
What Runlayer can see and stop in Cursor
Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.
Gateway policy (available)
Every Glean call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.
Block output after it runs (available)
Runlayer can block a tool’s output before Cursor’s model sees it.
Redact output in place (not available)
Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Cursor
- Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
- The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.
Frequently asked questions
Connect more