BackplanesBook your demo

AI agent security

Decide what your AI agents are allowed to do.

Write it in a sentence. Backplanes holds it across every agent, tool and server, and records every decision.

See it live, on your own intentions. Like:

  • “Only engineering’s agents touch production.”
  • “Customer data only goes to approved services.”
  • “Nothing destructive runs without a human confirming it.”
Book your demoor start free

One install · No code changes · Free to start

Declared intentions

6 declared

2 block at the gate. The rest watch and flag.

  1. 1

    Only engineering’s agents touch production systems and databases.

    286 flagged this weekNotifies
  2. 2

    Card data never goes to unapproved payment providers.

    1 flagged this weekNotifies
  3. 3

    Customer personal data only goes to services approved to handle it.

    Logs
  4. 4

    Credentials and secrets never leave to destinations we haven’t approved.

    Notifies
  5. 5

    Nothing destructive runs without a human confirming it.

    First catch · todayBlocks
  6. 6

    Agents only use tools and code we’ve verified, except in security engineering.

    Blocks

Sample organization · one week

Works with

  • Claude Code
  • Codex
  • Cursor

and your own agents, through our SDK

On the record

Deterministic controls placed outside the agent’s reasoning loop, including limits on tool access and permitted actions that cannot be overridden through context manipulation, remain valuable for mitigating harmful security outcomes.
Frontier Model ForumEmerging Security Practices for AI AgentsJune 2026Read the document

In your demo

Your intentions, held live.

  1. 1

    See what crosses them

    A week of agent activity reduced to the few things that touch your intentions. Everything else is accounted for and left alone.

    This week1,240 sessions
    • file-transfer.externalMCP servernew this week · 2 people
    • bulk-exportSkillspreading · now on 6 machines
    • paste.example.netDomainfirst seen · 1 session

    Three need a decision. Everything else was fine.

  2. 2

    Trace it to the events

    Which agent, which record, when, and in what mode. The briefing says what happened and how many decisions are owed.

    Investigating

    Production reads by Customer Success, a team outside engineering.

    48 decisions owed. Every read is read only, small, and tied to a support ticket. A narrow exception would cover it without opening the rest of production.

    What
    48 reads · 1 table
    Window
    30 days
    Coverage
    33 of 34 agents reporting
    ● Observing, not blocking
    48 reads4 agentsfrom customer_profiles

    Matching events · newest first

    • CUS-•••••-5203 · Willow-03
      Outcome
      Read completed
      Mode
      Observe
      State
      Needs a decision
    • CUS-•••••-5221 · Juno-06
    • CUS-•••••-5218 · Juno-06
    • CUS-•••••-5235 · Bramble-05
  3. 3

    Decide once. It holds.

    Backplanes proposes the narrowest change that fits. You see exactly what it would do, then monitor, warn or block from there.

    Production data · new pattern

    New this week

    Customer Success agents have started reading a single production database

    Your intentionOnly engineering’s agents touch production systems and databases.

    48 lookups4 agentsfrom prod-db · customer_profiles

    read only · each tied to a support ticket · since Monday

    What should the intention allow?

    Any Customer Success agent5 agents today, and anyone added to the team later.
    Read the customer_profiles tableMatches what they did this week.
    Just these 4 agentsThe ones seen this week.
    Everything in production, read and writeFar more than they used this week.
    BeforeOnly engineering’s agents touch production systems and databases.AfterOnly engineering’s agents touch production systems and databases, except Customer Success agents can read the customer_profiles table.

    48 Customer Success lookups stop flagging. 238 stay flagged: Marketing 142, Sales 61, Finance 35.

    Update the intention

Book your demo

Before you book

Three things security teams ask.

Q1

Does a model decide what gets blocked?

No. Models help draft controls from your activity. Deterministic code enforces them, so the same action gets the same answer every time.

Q2

Will this slow my developers down?

Controls start in monitor mode, so nothing is stopped until your team decides it should be. Warnings tell the developer why in the moment.

Q3

What do I need for the demo?

Two or three things your agents should never do, in a sentence each. We show you live how Backplanes would hold them.

Who builds Backplanes

Built by the people who kept Gmail safe and led the standard that authenticates email.

Seth Blank · Neil Kumaran · Nick Vlku

Book your demo

See Backplanes hold your own intentions.

Tell us who you are and one thing your agents should never do. We'll come back within one business day to set up a live demo built around it.

Prefer email? hello@backplanes.com.