Policy & Enforcement
Source: app.qpoint.io/security/policy
qcontrol observes every action through the proxy today. Below is what an enforcing policy would have intervened on — a dry run from data already collected in audit mode.
Egress & weak-TLS are real would-block counts. Tool/MCP and file numbers are totals a policy could scope/gate — not block counts.
Would Block
19
Would Scope
312
Flagged Runs
5
Enforcement mode
AuditAssistEnforce
Assist / Enforce projectedAudit → Assist → Automate. Audit is live; Assist (inline approvals) and Enforce (block at execution) reuse the same proxy with policy added.
Enforcement rules — dry run
Egress allow-list
v1
Flows Governed
847
Compliance
97
%
Violations
14
Tool / MCP allow-list
v1
Flows Governed
312
Compliance
100
%
Violations
0
Human-in-the-loop
v1
Flows Governed
96
Compliance
94
%
Violations
5
Kill switch roadmap
Instantly revoke an agent's autonomy to zero on incident.