Extensibility model

Bring your security process without advertising someone else’s product.

ChaosEngine models approved actions, scripts, agents, configurations and outputs as governed building blocks. Runtime readiness is verified against the selected worker environment.

A catalog entry is not proof that a binary is installed or executable on a particular worker. Early-access onboarding confirms the registered tool, worker dependencies and runtime behavior before a workflow is executed.
01Catalog action

Registered tool actions

Reference an approved action with its command contract, runtime requirements and organization access.

02Custom logic

Script nodes

Add deliberately configured transformation, filtering or orchestration logic inside the workflow graph.

03Assisted analysis

Agent nodes

Use an approved agent definition for analysis while retaining its place in the workflow and execution record.

04Runtime context

Configurations

Keep reusable runtime configuration governed separately from the workflow that consumes it.

05Result contract

Structured outputs

Describe JSON, JSONL or text outputs and table columns for consistent downstream review.

06Automation surface

MCP access

Operate supported scopes, workflows, resources, approvals and executions through the authenticated MCP surface.