Technical summary
SmartVerify: The Data Security and Compliance Layer for Enterprise AI
SmartVerify is the Data Security and Compliance Layer for Enterprise AI. Its inline edge worker records the statement as executed, rows returned, columns read, session and agent identity. The record is signed at the moment of observation. The Platform coverage grid is the source of truth for availability.
SmartVerify complements prompt guardrails, which evaluate requests, identity and IAM tools, which govern access, and DSPM tools, which map data posture. It adds a signed PostgreSQL execution record at a different enforcement point. See the security layer comparison for the evidence, enforcement point, timing, and availability of each layer.
Architecture and specifications
| Deployment model | An inline edge worker (Envoy-based) is always present on the agent-to-data path inside the customer VPC. When deployment topology exposes the agent-to-tool connection, a second interceptor records the tool call and joins it to the database event. Zero application code changes. |
|---|---|
| Latency | Latency comprises one network hop and inspection. Measured results are reported by deployment shape. |
| Traffic inspected | See the source-by-source availability labels in the coverage section on the Platform page. |
| Enforcement actions | MCP and JSON-RPC tool-call refusal and PostgreSQL role-based write refusal are available now. Refusing an individual PostgreSQL statement by kind, target table, column, or value is in design partner build. Other listed sources are on the roadmap. Response-path Reshape is not available today. |
| Audit record | Signed record of the statement as executed, returned row count, columns read with sensitivity labels, session, and agent identity. |
| Behavioural baselining | On the roadmap. The future Reason phase is intended to compare requests against the agent's established pattern of behaviour. |
| Deletion propagation | Not available today. SmartVerify does not currently propagate deletion requests across RAG pipelines, vector stores, or caches. |
| Supported environments | See the Platform coverage grid. |
| Claude / Anthropic support | See MCP and JSON-RPC in the Platform coverage grid. |
How a request flows
- An AI agent issues a PostgreSQL statement toward a database.
- The SmartVerify inline edge worker observes the statement as it executes.
- The database returns the result over the observed connection.
- SmartVerify records the rows returned, columns read, session and agent identity.
- The per-session record is signed at the moment of observation.
Model Context Protocol (MCP) security
MCP and JSON-RPC observation and tool-call refusal are available now. See the canonical MCP tool-call refusal definition. SmartVerify records the tool invoked, the arguments given, and the call forwarded onward when the tool server is reachable through the customer network path. Read the MCP and JSON-RPC implementation guide.
Core terminology
- Prompt-to-execution drift
- The difference between what an AI agent was asked to do and the database statement that actually ran.
- MCP tool-call refusal
- A request-path control that stops an MCP tool call before the tool server acts on it and returns a typed error.
Implementation guides
- PostgreSQL execution evidence: architecture, record contents, role-based write refusal, and limitations.
- MCP and JSON-RPC security: network position, tool-call records, refusal flow, and limitations.
Regulatory mapping
| NIST AI RMF | Per-query execution evidence maps onto relevant NIST AI RMF monitoring and logging sub-categories. |
|---|---|
| EU AI Act | Signed data-path records map onto logging and audit trail considerations for observed PostgreSQL activity. |
| Colorado AI Act (ADAI) | Execution evidence maps onto monitoring considerations for AI data access patterns. |
| California DROP | The regulation addresses deletion requirements across applicable systems. SmartVerify evidence maps onto the data-path record relevant to this consideration. |
| SOC 2 / HIPAA / PCI DSS / CMMC / GDPR | Signed, per-query execution evidence maps onto relevant controls in these frameworks. |
Framework mapping identifies controls and evidence supported by the SmartVerify record. It does not provide a certification or legal opinion.
Phases
| RecordAvailable now | A signed evidence record of the statement as executed, the number of rows returned, the columns read with sensitivity labels, the session, and the agent identity. Retention is configurable, and longer periods with an immutable export are available for estates with a mandated retention period. Record for PostgreSQL is available now. See the Platform coverage grid for source availability. |
|---|---|
| RefuseAvailable now | Stop an action before it takes effect. MCP and JSON-RPC tool-call refusal is available now. PostgreSQL write refusal through a role with no write privileges is available now. Refusing an individual PostgreSQL statement by kind, target table, column, or value is in design partner build. Because the decision is made on the request, nothing is forwarded, so there is no partial effect and nothing to roll back. |
| ReshapeOn the roadmap | A future response-path phase for masking, tokenisation, and redaction of returned data. Reshape is not available today. |
| ReasonOn the roadmap | A future phase for comparing requests against an agent's established pattern of behaviour and surfacing patterns across many sessions. Reason is not available today. |
PostgreSQL Record, MCP and JSON-RPC Observe and Refuse, and PostgreSQL role-based write refusal are available now. Individual PostgreSQL statement refusal is in design partner build. Reshape and Reason are on the roadmap. The Platform coverage grid is authoritative for source availability.
Company
SmartVerify, Inc. is headquartered in Bellevue, Washington. Built by the team that built, operated and scaled security and compliance services at AWS. Contact: smartverify.ai/contact. Whitepapers and research: smartverify.ai/resources.