Published 22 October 2026 · dotNew Labs
AI agents become useful when they can look things up and take actions in real systems. In healthcare and finance that is exactly where the risk sits. The controls below are not exotic. They are the same ideas you already apply to people, applied to software that acts on someone's behalf.
Every request should carry the signed-in user's identity, and the agent should get that user's permissions and nothing more. A shared service account that can read every record turns one clever prompt into a data breach.
HIPAA's minimum-necessary idea applies well beyond healthcare: give the model only the fields the task needs. Mask identifiers where the task doesn't need them, and keep full records inside your systems.
Log who asked, which tools the agent called, with what inputs, and what came back. Keep logs where your security team already looks, and sample them every week while the agent is new.
Text inside a document, email or web page can try to instruct the agent. Treat anything the agent reads as data, not orders. Limit what any single action can do, so a tricked agent can't do much harm.
Write a set of realistic questions with known right answers, including ones the agent should refuse. Run them before launch and after every change to the model, prompts or tools.
We offer a free 20-minute scan of one app: what it runs on, what's risky, and the shortest safe path forward. You keep a short written summary whether or not you hire us.
Book a free scanOr email contact@dotnewlabs.ai