AgentVisor™
Containment and Runtime Control · Healthcare
Contain AI Agents.
Control Every External Action.
AgentVisor runs AI agents inside a contained execution environment and controls what they can reach beyond it. When an agent attempts to access protected health information, invoke a tool, call an EHR or internal service, use a credential, or connect to a network, AgentVisor evaluates the attempted action against organizational policy before allowing or denying it.
AI agents are moving into documentation, prior authorization, claims, care coordination, patient engagement, and other healthcare workflows. As their autonomy increases, healthcare organizations and technology providers need more than visibility into what agents have done. They need an enforceable way to contain agents, control their external actions, and prevent activity that exceeds their authority.
HIPAA Security Rule
HIPAA Privacy Rule
Enterprise Security Reviews
Regulatory Context
The HIPAA Security Rule requires covered entities and business associates to protect electronic protected health information through appropriate administrative, physical, and technical safeguards, including access controls, audit controls, authentication, integrity protections, and transmission security. The HIPAA Privacy Rule generally requires reasonable efforts to limit uses, disclosures, and requests for protected health information to the minimum necessary for the intended purpose.
The Problem: Autonomy Changes the Risk
Traditional access controls were designed for people and deterministic applications. AI agents make decisions at runtime, combine tools dynamically, and take paths their developers may not have anticipated.
Excessive Authority
Agents may inherit application, service-account, or user permissions that provide broader access to PHI and connected systems than a particular action requires.
Unpredictable Actions
Changing context, prompt injection, flawed reasoning, or tool misuse can cause an agent to attempt actions outside its intended clinical or administrative function.
PHI Exposure
Agents may attempt to retrieve, combine, or transmit patient information beyond their authorized access.
Accountability Gaps
Application logs may show that an action occurred without showing which agent attempted it, what authority was evaluated, which policy applied, or why the action was allowed.
The AgentVisor™ Approach
AgentVisor combines contained execution with policy enforcement at the boundary between the agent and healthcare data, tools, services, and systems.
Contained Agent Execution
Run agents inside a sandboxed environment that limits direct access to networks, credentials, data stores, tools, and external services.
Policy-Enforced Boundary
Every attempt to act outside the contained environment is evaluated against organizational policy before it is allowed to proceed.
Complete Agent Visibility
See which agents are operating, what external actions they attempt, which resources they try to reach, and whether each action is allowed or denied.
Defensible Audit Evidence
Record the acting principal, attempted operation, target resource, relevant context, applicable policy, and enforcement outcome.
Authority Is Not Determined by Agent Reasoning
Prompts can be manipulated. Models change. Agents can take paths their developers did not anticipate. AgentVisor contains the agent and enforces organizational policy at the boundary. The agent can determine what action to attempt. It cannot determine whether that action is authorized.
Intelligence decides what. Authority decides whether.
AgentVisor™
Containment and Runtime Control · Healthcare
Containment With Continuous Authorization
AgentVisor controls what AI agents can access beyond their contained execution environment. Every attempted external action is evaluated against organizational policy, allowed or denied, and recorded with its decision context.
How It Works
1
The Agent Operates Inside Containment
The agent runs inside a sandboxed environment without unrestricted access to external networks, credentials, patient information, tools, or services.
›
2
The Agent Attempts an External Action
The agent attempts to retrieve patient information, invoke a tool, call an EHR or internal service, use a credential, or reach another resource outside the contained environment.
›
3
AgentVisor Evaluates the Attempted Action
AgentVisor evaluates the action against policy using the acting principal, attempted operation, target resource, and relevant context.
›
4
AgentVisor Allows or Denies the Action
If policy permits the action, AgentVisor allows it to proceed. If not, it blocks the action. The attempt, evaluation, and outcome are recorded.
From General Access to Contained, Action-Level Control
Control Area
Conventional Approach
With AgentVisor
Agent execution
Runs within the application environment
Runs inside a contained environment
PHI access
Inherited from application or service-account permissions
Evaluated for every attempted external action
Policy
Distributed across prompts and application code
Enforced independently at the containment boundary
Credentials
Available within the execution environment
Brokered outside the agent runtime
Enforcement
Dependent on agent or application behavior
Applied before external action proceeds
Audit evidence
Reconstructed across multiple logs
Attempt, policy evaluation, and outcome recorded together
Built for Healthcare Control Requirements
Access Control
Determine whether a specific agent is authorized to perform a specific action involving PHI, an application, or a connected healthcare system.
Minimum-Necessary Access
Use identity, action, resource, context, and additional claims to limit the data and systems an agent can reach.
Audit Controls
Maintain evidence showing what an agent attempted, which policy governed the action, what decision was made, and whether the action proceeded.
Transmission and System Access
Enforce policy before agents transmit information or interact with EHRs, APIs, internal services, and other connected systems.
Business-Associate and Customer Assurance
Demonstrate how agents are contained, how external actions are controlled, and how policy decisions are recorded when supporting healthcare customers and workflows involving PHI.
Control That Remains With the Organization
AgentVisor is designed for deployment within existing on-premises, private-cloud, and hybrid environments. Customer data, policies, agent activity, and decision records remain within the customer-controlled environment. Healthcare organizations and technology providers retain control over where agents execute, where policy is enforced, and where operational evidence is stored.
Move From Observing Agents to Containing and Controlling Them
AgentVisor gives healthcare organizations and technology providers an enforceable way to contain autonomous systems and control every action they attempt beyond the containment boundary.