Connect Cloudflare Digital Experience Monitoring to Windsurf
Give Windsurf governed access to Cloudflare Digital Experience Monitoring through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Cloudflare Digital Experience Monitoring to Windsurf in four steps
Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.
- 1
Approve Cloudflare Digital Experience Monitoring in Runlayer
Add Cloudflare Digital Experience Monitoring from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Windsurf to Runlayer
Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Cloudflare Digital Experience Monitoring’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Windsurf setup guide - 3
Sign in to Cloudflare Digital Experience Monitoring
Sign in the way Cloudflare Digital Experience Monitoring requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Cloudflare Digital Experience Monitoring from Windsurf
Cloudflare Digital Experience Monitoring’s approved tools appear in Windsurf. Every call is checked against policy and recorded.
Tools
Cloudflare Digital Experience Monitoring tools in Windsurf
Cloudflare Digital Experience Monitoring reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Windsurf
Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.
Gateway policy (available)
Every Cloudflare Digital Experience Monitoring call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Windsurf 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 Windsurf runs it.
Block output after it runs (not available)
Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.
In Windsurf
- Enforcement needs Windsurf 1.12.31 or newer.
- When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.
Frequently asked questions
Connect more