-
Notifications
You must be signed in to change notification settings - Fork 1
Capabilities
Krishna Kishor Tirupati edited this page May 13, 2026
·
1 revision
PolicyAware is a policy-aware control plane for governed AI execution. The capabilities below are documented independently so users can adopt one feature at a time.
Each capability guide includes copy/paste code, YAML examples, and API tables that show the important classes, methods, result fields, and policy fields.
| Category | Capability | Primary APIs |
|---|---|---|
| Data protection | Detect and redact PII, PHI, secrets, and sensitive strings |
DataProtectionEngine, PresidioPIIClassifier
|
| Policy enforcement | Decide allow, deny, conditional allow, or approval required |
PolicyEngine, PolicySchemaValidator
|
| Gateway orchestration | Run request through data checks, risk, policy, routing, eval, audit |
Gateway, GatewayRequest
|
| Risk classification | Score requests as low, medium, high, or critical | RiskClassifier |
| Model routing | Select compliant model/provider by region, cost, risk, capability |
ModelRouter, ProviderRegistry
|
| Provider adapters | Call local or external model backends |
SimulatedProvider, provider adapters |
| Tool governance | Govern MCP/agent connector and action permissions |
ToolPolicyEngine, ToolRegistry
|
| Evaluation | Check leakage, citations, policy consistency, golden datasets |
RuntimeEvaluator, EvalSuiteRunner
|
| Audit | Persist traces, replay requests, generate evidence bundles |
AuditLogger, SQLiteAuditLogger, AuditBundleWriter, TraceViewer
|
| Observability | Export local traces as Prometheus or OpenTelemetry-shaped data |
PrometheusExporter, OpenTelemetryJsonExporter
|
| ML-assisted signals | Add optional PII, prompt-injection, domain/risk classifier signals |
CompositeMLClassifier, MLSignal, ML adapters |
- Data Protection
- Ready-To-Use YAML Policies
- YAML Policy Templates
- Policy Enforcement
- Gateway Orchestration
- Risk Classification
- Model Routing And Providers
- Provider Adapter Examples
- Tool Governance
- Evaluation
- Audit And Observability
- ML-Assisted Signals
| Guide | API Tables Included |
|---|---|
| Data Protection | Main APIs, DataFindings result fields, policy fields |
| Policy Enforcement | Main APIs, PolicyDecision result fields, YAML policy context fields |
| Gateway Orchestration | Main APIs, GatewayRequest fields, GatewayResponse fields |
| Risk Classification | Main APIs, RiskAssessment result fields, common risk inputs |
| Model Routing And Providers | Main APIs, ModelCandidate fields, RouteDecision result fields, provider names |
| Tool Governance | Main APIs, ToolCallRequest fields, ToolDecision result fields |
| Evaluation | Main APIs, EvalResult fields, EvalReport fields, eval case YAML fields |
| Audit And Observability | Main APIs, AuditTrace fields, exporter APIs |
| ML-Assisted Signals | Main APIs, MLSignal fields, YAML policy fields |
- Start with
DataProtectionEnginefor simple string checks. - Add a YAML policy and test
PolicyEngine. - Use
Gatewayfor complete request handling. - Add
RiskClassifier,ModelRouter, and audit storage. - Add tool governance for agents.
- Add optional ML signals only after the rules-based path is understood.
- Home
- Capabilities
- Copy-Paste Examples
- Comparison
- SEO And Distribution
- Ready-To-Use YAML
- Data Protection
- Policy Enforcement
- Gateway Orchestration
- Risk Classification
- Model Routing and Providers
- Tool Governance
- Evaluation
- Audit and Observability
- ML-Assisted Signals
- Installation
- Quick Start
- Architecture
- CLI Reference
- ML Integrations
- Provider Adapter Examples
- YAML Policy Templates