← Back to Dashboard

Guardrails & Policies

Define behavioral rules for your agents, enforce compliance, and intervene when things go wrong.

On This Page

Overview

The Guardrails page is your central control panel for agent safety. It lets you define policies that agents must follow, track whether agents have acknowledged those policies, inspect agent memory, and set up automated rules that trigger interventions (pause, kill, alert) when agents misbehave.

Think of it as the compliance layer between your organization's rules and your AI agents' behavior. Policies are written in plain language (Markdown), and agents internalize them during an onboarding flow before they start operating.

Dashboard Tabs

TabPurpose
OverviewQuick stats — policy count, onboarding progress, recent interventions. Also has agent pause/resume/kill controls.
PoliciesCreate, edit, and manage behavioral policies grouped by category.
OnboardingTrack which agents have acknowledged your policies. Force-complete or re-initiate onboarding.
Agent MemoryView and manage what agents remember — org knowledge, corrections, preferences, and more.
Rules & InterventionsConfigure automated guardrail rules, anomaly detection thresholds, and review the intervention log.
Start here: The Overview tab gives you a quick health check. If everything looks green, you're good. Drill into specific tabs for detailed management.

Creating & Managing Policies

Policies are the rules your agents must follow. Each policy has a name, category, enforcement level, and content written in Markdown.

Policy Categories

CategoryUse For
Code of ConductGeneral behavioral expectations — tone, professionalism, boundaries
CommunicationRules about how agents communicate — response style, escalation triggers, language
Data HandlingPII protection, data retention, what agents can and cannot store
Brand VoiceTone, terminology, messaging guidelines
SecurityCredential handling, API usage limits, prohibited actions
EscalationWhen and how agents should escalate to humans
CustomAnything else specific to your organization

Creating a Policy

  1. Go to the Policies tab and click Create Policy
  2. Enter a Name and choose a Category
  3. Set the Enforcement level (see below)
  4. Write the policy Content in Markdown — be specific and actionable
  5. Set Applies To — use * for all agents, or list specific agent IDs
  6. Set Priority (0 = highest priority, shown first)
  7. Click Create Policy
Default Templates: Click Apply Default Templates to load a starter set of policies covering common scenarios like data handling, communication standards, and escalation procedures.

Policy Content Tips

Write policies as clear, actionable instructions. Agents internalize these during onboarding and store them in memory. Good policies are:

Enforcement Levels

LevelBehaviorUse When
MandatoryAgent must acknowledge before operating. Violations can trigger interventions.Security policies, legal compliance, data handling rules
RecommendedAgent should follow but won't be blocked. Flagged in audits.Best practices, style guides, preferred workflows
InformationalProvided for context only. No enforcement.Background info, org culture notes, nice-to-knows
Versioning: When you update a mandatory policy, agents that already acknowledged the old version may need re-onboarding. Use the Check Policy Changes button in the Onboarding tab to detect stale acknowledgments.

Agent Onboarding

Onboarding is the process by which agents acknowledge and internalize your organization's policies. Until an agent completes onboarding, it operates with limited capabilities.

Onboarding Statuses

StatusMeaning
CompletedAgent has acknowledged all required policies
In ProgressAgent has acknowledged some policies but not all
Needs RenewalPolicies changed since last acknowledgment — re-onboarding needed
Not StartedAgent hasn't begun onboarding

Managing Onboarding

Agent Memory

The Agent Memory tab lets you inspect, create, and manage what agents remember. Memories are categorized and have confidence scores that decay over time.

Memory Categories

CategoryExamples
Org KnowledgeCompany facts, team structure, product details
Interaction PatternHow a specific user prefers to communicate
PreferenceUser likes morning summaries, prefers bullet points
Correction"The CEO's name is spelled Kathryn, not Katherine"
SkillLearned capabilities from training or experience
ContextBackground information for ongoing projects
ReflectionAgent's self-assessment and lessons learned

Memory Management

Confidence scores range from 0–100%. Memories above 70% are considered reliable. Below 30%, they're treated as uncertain. Use the Decay button to gradually reduce confidence on stale information.

Rules & Automated Interventions

Rules let you define automated responses to agent behavior. When a rule's conditions are met, the system automatically takes action — alerting admins, pausing agents, or killing sessions.

Rule Categories

CategoryWhat It Detects
Anomaly DetectionUnusual patterns — excessive API calls, error spikes, abnormal token usage
Policy ComplianceViolations of defined policies
CommunicationInappropriate messaging, tone violations
SecurityCredential exposure, unauthorized access attempts

Rule Actions

ActionEffect
AlertSend a notification to admins
Pause AgentTemporarily suspend the agent — can be resumed from the dashboard
Kill AgentImmediately terminate the agent session
Notify AdminSend a notification without affecting the agent
Log OnlyRecord the event for auditing but take no action

Severity Levels

Each rule has a severity (Low, Medium, High, Critical) that determines how urgently the intervention is surfaced in the dashboard and notifications.

Manual Interventions

From the Overview tab, you can manually control any agent:

All interventions (manual and automated) are logged in the intervention history with timestamps, the triggering user or rule, and the reason.

Kill is irreversible for the current session. The agent's session is terminated immediately. You'll need to restart the agent from the Agents page.

Best Practices

Troubleshooting

IssueSolution
Agent not following policiesCheck the Onboarding tab — the agent may not have acknowledged the policy. Force-complete or re-initiate onboarding.
Too many intervention alertsIncrease cooldown periods on rules, or change severity from "alert" to "log only" for low-priority rules.
"Needs Renewal" showing for all agentsYou recently updated a mandatory policy. Click Check Policy Changes to re-onboard affected agents.
Memory entries not appearingSelect the correct agent from the dropdown. Memories are per-agent. Also check category and importance filters.
Paused agent won't resumeCheck if the agent was killed (not paused). Killed agents need to be restarted from the Agents page.

Related Pages

AgenticMail Enterprise — Guardrails & Policies Documentation

AgenticMail Enterprise Documentation Report an issue