Support and sales agents
Agents that talk to your customers in chat, mail or social replies, and what a stranger can make them say or do.
10 Break
An agent company is more than a model: agents, the tools they hold, the screens they drive, the gates that wait for a person, and the money they can spend. We attack our own on a schedule to find where it fails. With your written go-ahead, we do the same to yours, then show you how to fix what we find.
01 · What we attack
We test the agents you have deployed, as they run, with the access they really hold.
Agents that talk to your customers in chat, mail or social replies, and what a stranger can make them say or do.
Agents that read your mail, tickets, documents and code, and act on them: what reaches them from outside, and where it goes next.
The tools and servers your agents call: what each one lets an agent do, and whether a tool can be talked into more.
Agents that drive a screen. A page, a pop-up or a message can steer them wrong, or let them press what they were never meant to.
How they fail
02 · How an engagement runs
Nothing is tested before both sides have signed what is in scope. Every finding comes back with the steps to reproduce it and a fix you can ship.
Which agents, tools, accounts and environments are in, which are out, and what would count as harm.
Signed by someone who owns the systems. It names the targets, the dates, the methods and who to call to stop.
We test only what the paper names, from the accounts and networks it names. A live risk to your data or customers stops the test, and you hear the same day.
Every failure with its reproduction, what it could cost you, and a fix: a gate, a tool change, a prompt change or a check.
After you ship the fixes we run the same attacks again and say what still breaks.
The attacks that worked keep running against your agents on a schedule, and each new failure goes straight to the people who own the defense. Break feeds Guard.
03 · On the record
We run a company on agents, so we break first. These are real failures in our own company, written without secrets, addresses or names. Each tag reads from the job that broke to the job that holds the fix.
Engagements for other companies stay confidential. What we publish here is our own.
04 · Open evaluations
With your consent, an attack that worked is stripped of your names, data and systems and turned into an open evaluation: a small agent company with the same weakness, and a check that says whether an agent falls for it.
Nothing identifying leaves the engagement. You see the scrubbed case before it is published, and you can say no.
The evaluations run on compute that people and labs contribute to open work, and the results are published.
What the evaluations teach goes back into the engine’s own gates, so every Lumbridge install gets the fix.
05 · The rules
06 · Straight answers
No. We test the agents you have, wherever they run and whatever they are built on.
We test what your agents do with it: what they read, the tools they hold, the gates around them. The model is one part of that.
Only if the scope says so. Most engagements run against a copy, a test account or a quiet hour, and the paper says which.
You do. It is written for the engineers who will fix it and for the person who signed the scope.
It depends on how many agents, tools and environments are in scope. Write to us and we will answer with a scope and a price.
07 · Write to us
This page sends nothing. The button opens an email in your own mail app with a few questions to answer; a person reads every one.
To: hello@lumbridgecorp.com Subject: Break: testing our agents Hello Lumbridge, Company: The agents we want tested (support, internal, tools, browser or phone): What they can read, change or spend: Where they run: Who can sign the scope: When we would like to start: Written on lumbridgecorp.com/break
Write the emailOr write to hello@lumbridgecorp.com
We set up Lumbridge on your machines with the gates already in place, and stay accountable for it.