Keep your autonomous agents secure
Give agents enough room to work, but not to roam.
Tie execution to approved tools and boundaries.
- Allow or deny command classes and runtime behavior.
- Set data boundaries around repositories, prompts, and artifacts.
Runtime security
The security model custom-built for agents.
FAQ
Frequently asked questions.
Can we block dangerous commands?
Yes. Command allow/deny controls are part of runtime guardrails.
Can agents read all company data?
No. Access should be scoped through environment, repository, tool, and data-boundary policy.
Does this replace code review?
No. Runtime controls reduce risk during execution; review still governs what gets accepted.
Can policies vary by project?
The model is designed for organization defaults plus project and workflow-level controls.
Other platform pieces.
Rest of platform layer.