Integrations/CircleCI

Control what your AI agents do in CircleCI.

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

Request early accessSee how it works →
CircleCI
Build Agent
app-backend ProjectOffReadFull use
web ProjectOffReadFull use
payments ProjectOffReadFull use
Delete contexts and secrets
What agents can do

Set what each agent can do in every project.

Each project gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the project or that it exists.
Read
Read-only
The agent can read pipelines, workflows, and jobs in that project. It can't change anything.
Full use
Run and update
The agent can trigger and rerun pipelines in that project.

Some actions stay off until explicitly turned on

Each one can leak credentials, remove your build config, or cancel running work, so it could override the limits set on individual projects.

Reading or deleting contexts and secretsCancelling running workflows or jobsDeleting environment variables
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 CircleCI a single time and chooses which projects it covers. Any project left out 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, trigger, and rerun pipelines in a single project
Example

A build pipeline agent.

A build agent triggers pipelines on app-backend and can read web, but it can't open the payments project or touch secrets.

app-backend ProjectOffReadFull use
web ProjectOffReadFull use
payments ProjectOffReadFull use

Manage access

ALLOWEDBuild Agent triggered a pipeline in app-backend
ALLOWEDBuild Agent read a workflow in web
BLOCKEDBuild Agent tried to open the payments project, 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 CircleCI, so they never hold your CircleCI keys and never reach CircleCI directly.

Everything runs through Bollard AI

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

Denied by default

Every project starts off-limits, and touching secrets 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 CircleCI 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 project or pipeline, and the decision. The record is readable and can't be edited after the fact.

Questions

CircleCI, answered.

Does connecting CircleCI hand Bollard AI all your projects?+
Only what's connected. An admin chooses which projects Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your build setup. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent read our secrets or cancel builds?+
Not unless you turn it on. Reading or deleting contexts and secrets, and cancelling running work, are held off by default, so an agent can trigger and read pipelines where you allow without ever touching secrets, 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 CircleCI 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 CircleCI, and the blocked attempt lands in the activity record with the reason.
How do we connect CircleCI?+
An admin connects the company's CircleCI once. Bollard AI seals the connection and builds the list of projects 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 CircleCI, 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 →