Integrations/Cloudflare

Control what your AI agents do in Cloudflare.

Let your team build AI agents for Cloudflare. Bollard AI controls what each one can do, area by area.

Request early accessSee how it works →
Cloudflare
Infra Agent
DNS records Account areaOffReadFull use
Cache Account areaOffReadFull use
Workers Account areaOffReadFull use
Deploy Workers scripts
What agents can do

Set what each agent can do across your Cloudflare account.

Each area of Cloudflare, like DNS, cache, or firewall, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see that part of your account.
Read
Read-only
The agent can read DNS records and settings in that area. It can't change anything.
Full use
Create and update
The agent can create and update records in that area, like adding a DNS record.

Some actions stay off until explicitly turned on

Each one can take a site down, change what runs at the edge, or remove a domain, so it could override the limits set elsewhere.

Deleting zones or DNS recordsDeploying or changing WorkersChanging firewall and WAF rules
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Cloudflare a single time. Bollard AI lays out the areas of your account, and anything you don't allow stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, create, and update records in a single area
Example

An infrastructure agent.

An infra agent updates DNS records and can read your cache settings, but it can't deploy Workers or change firewall rules.

DNS records Account areaOffReadFull use
Cache Account areaOffReadFull use
Workers Account areaOffReadFull use

Manage access

ALLOWEDInfra Agent added a record in DNS records
ALLOWEDInfra Agent read the Cache settings
BLOCKEDInfra Agent tried to deploy a Worker, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Cloudflare, so they never hold your Cloudflare keys and never reach Cloudflare directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Cloudflare. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every area starts off-limits, and deploying Workers is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Cloudflare keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which record or zone, and the decision. The record is readable and can't be edited after the fact.

Questions

Cloudflare, answered.

Does connecting Cloudflare hand Bollard AI your whole account?+
Only the areas you allow. An admin connects your Cloudflare, and you decide which areas, like DNS or cache, each agent can reach. Bollard AI doesn't browse or copy your account. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent take a site down or change what runs at the edge?+
Not unless you turn it on. Deploying Workers, deleting zones, and changing firewall rules are held off by default, so an agent can manage records where you allow without ever taking a site down, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Cloudflare keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Cloudflare, and the blocked attempt lands in the activity record with the reason.
How do we connect Cloudflare?+
An admin connects the company's Cloudflare once. Bollard AI seals the connection and lays out the areas of your account to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Cloudflare, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →