What is Vaultak Sentry?
When an AI agent runs on your systems, it can read files, make network requests, write to databases, and spawn other processes. Without governance, there is no way to know what it is doing or stop it if something goes wrong. Vaultak Sentry sits alongside the agent process and watches everything it does at the operating system level. It compares every action against a policy you define. If the agent does something it is not authorized to do, Sentry alerts you, pauses the agent, or automatically reverses the damage. The agent does not know Sentry is there. You do not need to touch the agent code at all.Before you start
You need:- A terminal application (Terminal on Mac, any terminal on Linux or Windows)
- Python 3.8 or higher installed
- A Vaultak account and API key from app.vaultak.com
Step 1: Install Vaultak Sentry
Step 2: Connect to your Vaultak account
Step 3: Check that everything is working
Step 4: Create a policy for your agent
A policy tells Sentry what your agent is authorized to do. Anything outside the policy is unauthorized.- data-pipeline: Agents that read and process data files
- coding-agent: Agents that write and execute code
- customer-support: Agents that interact with CRM or customer systems
- research-agent: Agents that browse the web and gather information
- hipaa-agent: Agents handling healthcare or patient data
- strict: Maximum restriction for sensitive environments
Step 5: Run your agent through Sentry
Before Sentry:Step 6: View your agent in the dashboard
Open app.vaultak.com. You will see your agent listed with every action it has taken, each one risk-scored and logged in real time.Attaching to an agent that is already running
First find the process ID:Response modes
Customizing your policy inline
Disabling specific monitors
What Sentry monitors
- File system: Every file your agent reads, writes, or deletes
- Network: Every connection your agent makes to external servers
- Processes: Every subprocess your agent spawns
- CPU: Spikes above 90% that may indicate runaway behavior
- Memory: Usage above 2GB that may indicate a memory leak or loop
- Database: Connections to database ports