Connect Pigment to Cursor
Give Cursor governed access to Pigment’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pigment to Cursor in four steps
Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.
- 1
Approve Pigment in Runlayer
Add Pigment 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, Pigment’s 101 tools show up in Cursor’s own tool list.
Cursor setup guide - 3
Sign in to Pigment
Sign in the way Pigment requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pigment from Cursor
Pigment’s approved tools appear in Cursor. Every call is checked against policy and recorded.
Tools
101 Pigment tools in Cursor
Runlayer policy decides which of these Cursor users can call.
Add list items
Add one or more new items (rows) to a dimension/list with their property values in a single operation.
Batch share blocks
Share multiple lists and metrics in a single operation, making them visible and usable across applications within the organization.
Calendar add time dimension
Add a new time dimension to existing Application calendar.
Create calendar
Creates a new gregorian calendar in the Pigment application.
Calendar expand
Expands or shrinks a calendar's date range.
Get calendar
Retrieves detailed configuration of a specific calendar.
Calendar remove time dimension
Remove a time dimension from the Application's calendar.
Clear widget preview
Removes the Draft View preview from a single Board widget for the current user, so the widget shows its saved View again.
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 Pigment 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