Skip to main content

Connect Cloudflare Workers Bindings to Zed

Give Zed governed access to Cloudflare Workers Bindings through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Cloudflare Workers Bindings to Zed in four steps

Admins approve the server once. Everyone in Zed then gets it through the same governed connection.

  1. 1

    Approve Cloudflare Workers Bindings in Runlayer

    Add Cloudflare Workers Bindings from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Zed to Runlayer

    Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Cloudflare Workers Bindings’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Zed setup guide
  3. 3

    Sign in to Cloudflare Workers Bindings

    Sign in the way Cloudflare Workers Bindings requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Cloudflare Workers Bindings from Zed

    Cloudflare Workers Bindings’s approved tools appear in Zed. Every call is checked against policy and recorded.

Tools

Cloudflare Workers Bindings tools in Zed

Cloudflare Workers Bindings reports its tools when your organization connects it, so the list depends on your deployment.

Control

What Runlayer can see and stop in Zed

Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.

  • Gateway policy (available)

    Every Cloudflare Workers Bindings call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination