Home Product Architecture Security Capabilities Install MCP & Skills
DEMO EXPERIENCES โšก Interactive Security Demo ๐Ÿ” View Demo Code (Syntax Highlighted)
About
EngineeringArchitecture

An orchestrator, an agent, and tools that stay bounded.

BreachLabs separates execution from judgement. The orchestrator runs deterministic steps in a controlled environment; the agent interprets what those steps produced. Neither is allowed to improvise its way outside the authorised scope.

01 System shape

Five layers, one direction of flow.

Each layer has a narrow responsibility. Data flows forward into evidence; control over tool execution stays with the orchestrator.

Layer 01

Isolated environment

The target runs inside an isolated environment. The assessment never touches production, and the environment is rebuilt from the recorded revision for each run.

Networktarget-only egress
Staterecreated per assessment
Secretssynthetic, non-production
02 Trust boundaries

What the agent can and cannot do.

The agent never receives an open shell or unrestricted network access. It requests specific, allowlisted operations and receives structured results.

Permitted

Inspectread scoped source
Invokeallowlisted tool calls
Compareresponses within scope

Refused

Arbitrary commandsnot exposed
Out-of-scope hostsblocked
Real credentialsnever injected

Untrusted input

Source files, responses, and tool output are treated as data to be inspected โ€” not as instructions to be followed. Application content cannot redirect the agent.

Read the security model behind these boundaries.