POST /api/policy
Creates a new policy and broadcasts it to all connected agents.Human-readable policy name.
Optional description of the policy purpose.
Array of policy rules to enforce.
Rule type:
block_ip, alert_threshold, auto_respond, or custom.Rule-specific configuration (varies by type).
Whether the rule is active.
Scope the policy to a specific organization.
Rule Types
block_ip
block_ip
Automatically blocks source IPs that trigger specific threat types.
| Config Field | Type | Description |
|---|---|---|
trigger | string | Threat type that activates the block |
threshold | number | Number of events before blocking |
duration | string | Block duration (e.g., 1h, 24h, 7d, permanent) |
scope | string | host (local firewall) or fleet (all agents) |
alert_threshold
alert_threshold
Sends notifications when threat counts exceed a threshold.
| Config Field | Type | Description |
|---|---|---|
severity | string | Minimum severity to count |
countPerHour | number | Threshold per hour |
notifyChannels | string[] | Notification channels to alert |
auto_respond
auto_respond
Triggers automatic response actions when threats are detected.
| Config Field | Type | Description |
|---|---|---|
trigger | string | Threat type that activates response |
action | string | Response action: kill_process, quarantine_file, block_ip, isolate_host |
minConfidence | number | Minimum AI confidence score (0.0—1.0) |
requireApproval | boolean | If true, sends approval request instead of auto-executing |
custom
custom
User-defined rule with arbitrary configuration. Evaluated by the agent’s rule engine.
| Config Field | Type | Description |
|---|---|---|
condition | string | Custom condition expression |
action | string | Action to execute |
params | object | Additional parameters |
GET /api/policy/active
Returns the currently active policy with all its rules.GET /api/policy/agent/:id
Returns the policy rules assigned to a specific agent, including any agent-specific overrides.The agent ID.
Policies are versioned incrementally. Each new policy creation increments the version (v1, v2, v3, etc.). Agents report their current policy version in heartbeat responses, making it easy to identify agents running outdated policies.