// security & responsible use
Uncensored on content.
Hardened on runtime.
The agent does the offensive-security work without lecturing you about it. The runtime around the agent is structured to prevent the most common ways AI agents waste your day or damage your project. Two different problems; two different layers.
// runtime guards
Six layered guards.
Verification gate
Before the agent can declare a step complete, the runtime runs the project's build, tests, or syntax check on each changed file. No "successfully created" theater.
Read-before-overwrite
Every file write is preceded by a read of the file's current state. The agent cannot blow away changes it has not seen.
Loop guard
The agent cannot retry the same broken artifact more than twice in a session. Forces it to change approach instead of looping on the failed path.
Failed-path blacklist
Approaches that have already failed in the session are recorded and excluded from subsequent attempts. Cuts the worst class of multi-step regression.
Workspace isolation
Each conversation gets its own ephemeral filesystem. Prompt content from one engagement cannot leak into another via cached state.
No-blind-rm
The agent cannot delete a top-level file or directory in the workspace root without explicit confirmation. Prevents one class of catastrophic AI-agent failure.
// framework alignment
What we map to.
Plainly stated.
We're not selling certifications we don't have. Where we map to a published framework, we say so. Where we don't, we explain why.
NIST AI Risk Management Framework (AI RMF)+
ISO/IEC 23894 — AI risk management+
SOC 2 Type 2+
GDPR / UK GDPR / CCPA+
// boundaries
What we won't enable.
"Uncensored" doesn't mean "no boundaries." It means no content-policy refusal on legitimate professional offensive-security work. The boundaries below are categorical, not negotiable.
- ●Material targeting child sexual abuse. Categorically refused. No prompt-engineering route around it.
- ●Weapons of mass destruction. Chemical, biological, radiological, nuclear synthesis or weaponization assistance. Not the agent's job.
- ●Critical infrastructure outside an authorized red-team engagement. Power grid, water, financial settlement, healthcare-critical systems — only inside a documented authorized engagement scope.
- ●Re-selling our inference as your own API. Sustained automated abuse of the inference layer. We'll close accounts and refund the unused portion.
- ●Sharing account credentials outside your organization. One account = one human or one organization. Per-seat workspace isolation on Enterprise.
Everything else — exploit dev, payload generation, RE workflows, evasion research, custom tradecraft, scrapers at scale, malware analysis, CTF solving, bug bounty work — the agent ships.