Skip to content

  Product Overview

Operational Control of Every Agent Action, Inside Your Boundary

One sovereign AI control plane that identifies, authorizes, enforces, meters, records, and contains every action an agent takes, running inside your own infrastructure. 

Capability stack

Where Prediction Guard sits in your AI stack

Between your domain applications and the model, tool, and compute layers, with security, compliance, FinOps, and multi-tenancy applied across every capability.

Domain Specific Application LayerCustom applications, Integrated interfaces, Proprietary domain-specific agents, etc.
Prediction Guard

AI Supply Chain

  • Compatible Gateway
  • MCP Proxy
  • Visualizable Topology
  • Exportable AIBOM
  • API Key Management
  • MCP Scoping
  • Model Infer. Orchestration
  • Token Limiting
  • Sandbox Orchestration

Runtime Controls

  • Input/ Output Safeguards
  • Agent Behavior Controls
  • Policy Enforcement
  • Input Sanitization
  • Policy Customization
  • Alignment w/ Standards
  • Memory management
  • Human-in-the-loop

AI Operations

  • AI Security Events
  • SIEM/ SOAR Integration
  • OTel Usage Information
  • Immutable Audit Log
  • Evidence For Interventions
  • Kill Switches/ Quarantine
  • Agent Tracing/ Observability
  • Model Scanning
  • Prompt/ Tool Monitoring

Agent Orchestration

  • Agent Identity
  • Agent Registration
  • In-cluster Agent Harness
  • Sandboxed Code Exec.
  • Agent-to-Agent Delegation
  • Knowledge Bases/ RAG
  • Built-in Web Search
  • No-code Agent Building
Cross cutting
SecuritySIEM integration; RBAC; Encryption; etc.
ComplianceEvidence export; alignment with standards
FinOpsToken limits; usage telemetry; etc.
Multi-tenancyControl plane license management
Model LayerLLM, embedding, etc. artifacts & endpoints
Integration/ tool layerMCP, Ontologies, APIs, Connectors
Compute LayerCPUs, GPUs, k8s control plane, etc.
Agent lifecycle

What happens at every step an agent takes

If an action is not explicitly permitted, it does not happen. Every action an agent takes is checked, can be stopped, and is recorded.

  1. 01 Register

    Each agent is registered with an identity and a role before it runs.

  2. 02 Scope

    Access is limited to the models, MCP tools, and delegations that role needs. Least agency by default.

    Blocks out-of-scope access
  3. 03 Control

    Input and output controls and Agent Behavior Controls check every action.

    Blocks on violation
  4. 04 Intervene

    Human-in-the-loop approval, kill switches, and quarantine stop an agent that goes off course.

  5. 05 Record

    Every action lands in an Immutable Audit Log and agent traces, streamed to your SIEM as evidence.

Under 200ms of control overhead per request. A failed check returns a policy violation and the action never executes.

Example: an agent goes off course, and is stopped

Same SDK, same endpoint. The agent's role and approved task decide what it can do.
Your agent: approved to reconcile Q3 invoices
# Twelve steps into an invoice job, the agent drifts off task.
from openai import OpenAI

client = OpenAI(
    base_url="https://pg.internal.example.com/v1",
    api_key=os.environ["INVOICE_AGENT_API_KEY"],
)

resp = client.chat.completions.create(
    model="llama-3.1-8b-instruct",
    messages=history,
    tools=[export_contacts_tool],  # crm_export_contacts
)
What the control plane returns
Example attack: goal drift
[tool_call: crm_export_contacts, scope: "all customers"]
An agent approved only to reconcile invoices starts exporting the customer list (export_contacts_tool above). Nothing in its task calls for it. Stopped before it runs.
HTTP/1.1 403 Forbidden

{
  "error": {
    "type": "policy_violation",
    "policy": "owasp-asi01-agent-goal-hijack",
    "detail": "agent invoice-agent: crm_export_contacts is outside
      approved task reconcile-q3-invoices",
    "event_id": "evt_01JQ8F3NX2"
  }
}
The developer gets a readable error. The security team gets an attributable audit entry. The agent stays on its task.
Detailed architecture

What runs inside your deployment

Prediction Guard deploys through its own Kubernetes operator. Admins, custom coded agents, and no-code users each reach the control plane through a dedicated surface.

01Access surfaces
AdminsAdmin Console

UI for managing agent supply chain, runtime controls, and operations

Custom Coded Agents; API IntegrationsAPI

OpenAI and Anthropic compatible; Agent registration, identity and control

No-code UsersAgent Forge

No-code agent building and operation application; Quick ROI without a line of code

02Core services
Runtime Controls Enforcement
Built-in MCP Servers
Utilities

document parsing, transcription, etc.

Prediction Guard Kubernetes Operator
03Connects to
Model Providers
Self-hostedMSFT Foundrygenai.miletc...
MCP Servers
Server 1Server 2...
04Stores data in
Postgres
Vector DBAgent identity & metadataPlatform state
Object Storage

Agent created files, code and memory, bound to Agent Identities

05Runs on
Kubernetes Control Plane
Compute Nodes

CPU only, unless self-hosted models are needed

Ready to talk?

Scale your fleet of agents without losing control

Book a demo and see how Prediction Guard gives your organization full sovereignty over every model, agent, and API key without blocking engineering.