Connect ZoomInfo to Cursor
Give Cursor governed access to ZoomInfo’s 24 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add ZoomInfo to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve ZoomInfo in Runlayer
Add ZoomInfo 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, ZoomInfo’s 24 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to ZoomInfo
Sign in the way ZoomInfo requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use ZoomInfo from Cursor
ZoomInfo’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
24 ZoomInfo tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Account research
Research a company/account/organization using ZoomInfo market data with your CRM and conversation history.
Audience analysis
Compute answers about the contents of a GTM Studio audience.
Browse audiences
Browse GTM Studio audiences with basic metadata.
Browse engagements
Retrieve engagements (meetings and emails).
Contact research
Research a specific person/contact using ZoomInfo market data with your CRM and conversation history.
Conversation intelligence
Answers natural-language questions about calls, meetings, and emails, scoped to a single engagement, an account, or a contact.
Enrich companies
Enrich company data with comprehensive business intelligence from ZoomInfo's database.
Enrich company signals
Fetch multiple signal types for specific companies in a single request, enriching company details with Intent, News, and Scoops data.
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 ZoomInfo 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