Uncontrolled AI agents can exfiltrate personal data in seconds, jeopardizing LGPD compliance.
Why AI agents break LGPD rules today
Many organizations let autonomous agents run against production databases with a single service credential. The credential is often a long‑lived secret that multiple pipelines share. Because the agents connect directly to the database, every query bypasses any human review. No logs are kept that tie a specific data request to an individual requestor, and no field‑level masking is applied. When a data‑subject request arrives, the team cannot prove that the personal data was only accessed for a legitimate purpose, nor can they demonstrate that the access was time‑boxed.
The partial fix that still leaves gaps
Moving to non‑human identities and tightening IAM policies is a necessary step. Service accounts can be scoped to read‑only or write‑only roles, and tokens can be short‑lived. However, the request still travels straight to the target system. The gateway that could enforce additional controls is missing, so the system still lacks:
- Real‑time approval before a risky query runs.
- Inline masking of personal identifiers in query results.
- Immutable session recordings that auditors can replay.
- Continuous evidence that ties each data access to a verified identity.
These gaps mean that, even with proper identity management, the organization cannot satisfy LGPD’s requirement for detailed access logs and data protection measures.
How hoop.dev provides the missing data‑path controls
hoop.dev is a Layer 7 gateway that sits between AI agents and the infrastructure they query. By placing hoop.dev in the data path, every request passes through a single enforcement point. hoop.dev then applies the controls that LGPD expects:
- Just‑in‑time access: An agent’s request triggers an approval workflow. A designated reviewer can grant or deny the operation before any data leaves the target.
- Inline data masking: Sensitive fields such as CPF, RG, or email addresses are replaced with masked tokens in the response stream, ensuring that downstream systems never see raw personal data.
- Session recording: hoop.dev records the full protocol exchange, including the exact query and the masked response. The recordings are stored outside the agent’s environment, giving auditors a replayable audit trail.
- Per‑session audit logs: Each session is logged with the verified identity of the agent, the time of access, the approved purpose, and the outcome. The logs are immutable and can be exported to SIEM or compliance platforms.
Because hoop.dev is the only component that can block, mask, or approve a request, the enforcement outcomes exist solely because hoop.dev occupies the data path. The identity system (OIDC, SAML, service accounts) decides who the request is, but hoop.dev decides what the request can do.