Back to products
CtrlAI

CtrlAI

Transparent proxy that secures AI agents with guardrails

Overview

What it is

CTRL-AI v1 is a transparent HTTP proxy that sits between your AI agent and LLM provider, enforcing guardrails, auditing behavior, and blocking unsafe tool calls — with zero SDK modification required.

Intent

I need it when

Customize security rules for specific tools, file paths, commands, and URL patterns

CtrlAI uses a YAML-based rules engine supporting glob patterns for paths, regex for commands and URLs, substring matching for arguments, and per-agent scoping. Users can block specific tools (e.g., read, write, exec), match on file paths (**/.env), command patterns (rm -rf /), or URL domains without writing code.

Prevent AI agents from executing dangerous tool calls that could compromise security or privacy

CtrlAI intercepts LLM responses before they reach the agent SDK, evaluates tool calls against configurable guardrail rules (19 built-in rules covering file system, destructive commands, privacy, messaging), and blocks dangerous calls. This stops harmful actions like SSH key access, credential exfiltration, or shell command injection without modifying agent code.

Enforce per-agent security policies and kill switches for multi-agent deployments

CtrlAI supports per-agent rule configuration and kill switches via URL path routing (e.g., /provider/anthropic/agent/main/). Teams can apply different guardrail rules to different agents and instantly disable an agent's tool access without redeploying code.

Audit and log all tool calls made by AI agents for compliance and debugging

CtrlAI acts as a transparent HTTP proxy that logs every LLM request and response to a local audit directory. Users can review what tools were called, what arguments were passed, and what was blocked, enabling compliance reporting and troubleshooting without invasive code instrumentation.

Integrate guardrails into existing AI agent workflows without code changes

CtrlAI is a drop-in HTTP proxy that sits between agent SDK and LLM provider. Users only need to change the baseUrl in their agent config to point to CtrlAI (e.g., http://127.0.0.1:3100/provider/anthropic). The agent SDK sees no difference; all guardrail logic runs transparently in the proxy.

Drop

Not a fit when

  • User needs a managed SaaS solution with vendor support and uptime guarantees
  • User lacks Go 1.24+ runtime or cannot self-host infrastructure
  • User requires guardrails for LLM providers other than Anthropic and OpenAI
  • User needs real-time monitoring dashboards beyond the basic HTTP proxy dashboard
  • User operates in a regulated environment requiring formal compliance certifications or audit trails beyond local logging
Commercials

Pricing

Open source, free to use