PAGES
← all tools
◆ AI Security Posture & Discovery

Onyx Security

commercial

Onyx Security is a control plane that discovers, monitors and governs enterprise AI agents inline across browsers, coding assistants, cloud workloads and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers.

Summary

Onyx Security is a commercial control plane that discovers, monitors, and governs enterprise AI agents inline across browsers, coding assistants, cloud workloads, and MCP servers. It is built for platform engineers interested in agentic AI security, placing it within the field of AI governance tools. The project launched in 2024.

Onyx Security is a control plane that discovers, monitors and governs enterprise AI agents inline across browsers, coding assistants, cloud workloads and MCP servers.

How Onyx Security helps

Which AI agents are running across our browsers, coding assistants, cloud workloads and MCP servers?

inventories agent activity inline across those surfaces and reports where each one is running, rather than relying on a survey of teams

Which MCP servers are configured and talking to our systems right now?

discovers MCP servers in use across the environment and surfaces them as part of the governed inventory

Is an agent doing something outside what it was approved to do?

monitors agent behavior inline at runtime and flags actions that fall outside the governed policy

Can a coding assistant reach data or systems nobody signed off on?

governs agent access inline across coding assistants and cloud workloads, so ungoverned reach shows up rather than passing unnoticed

Which cloud workloads have an AI agent attached to them?

discovers agent presence across cloud workloads as part of the same inline inventory used for browsers and coding assistants

Should a given agent's access be shut down before it causes damage?

governs agents inline, so enforcement happens at the point of activity rather than through a separate after-the-fact review

all 6 features, with the evidence for each →

Languages

Not documented

Features

6 capabilities

Built from Onyx Security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Onyx Security offers you

  • Agentless deployment1
  • Web management console1
All capabilities 6 capabilities
Runtime guardrail enforcement shipped Evaluates prompts, responses, tool calls, and uploaded file text against enterprise AI security policies at the inference boundary, blocking sensitive data, credentials, prompt injection, jailbreaks, and risky content in real time. 3 releases · first seen Sep 2026

Also counts toward: Agentless deployment, Web management console

release

  • Returns a real-time allow-or-deny verdict at the inference boundary with no agent, proxy, or per-device installation required — coverage extends across Claude, Claude Code, Cowork, and connected tools from a single integration. announced · Oct 2026 · source · release history
  • Enforces Onyx runtime policies to block sensitive or regulated data exposure, credentials and secrets, intellectual property, prompt injection and jailbreak attempts, and risky content from agent tool results or connector responses. announced · Oct 2026 · source · release history
  • Blocked requests return the policy message configured in the Onyx console, with no wrapper redeploy required when enforcement rules change. announced · Sep 2026 · source · release history
Anthropic Claude Enterprise integration shipped Connects Onyx AI Guard to Anthropic Claude Enterprise inference hooks so every prompt, tool-call response, and uploaded-file text is screened by the same Onyx policy layer that governs other copilots, coding agents, SaaS AI applications, MCP servers, and AI gateways. 2 releases · first seen Oct 2026

release

  • Connects Onyx AI Guard to Anthropic Claude Enterprise inference hooks, so every prompt, tool-call response, and uploaded-file text is evaluated against enterprise AI security policies before reaching the model.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Oct 2026 · source · release history
  • Extends Onyx's Secure AI Control Plane into Claude's native inference path, so the same policy layer governing copilots, coding agents, SaaS AI applications, MCP servers, and AI gateways also governs Claude without a separate Claude-specific policy model. announced · Oct 2026 · source · release history
Per-request guardrail override shipped Allows teams to attach or test guardrail groups on individual requests without changing a model's default settings, using inline parameters or request headers. 1 release · 1 other source · first seen Sep 2026

release

  • Supports per-request guardrail attachment using llm_input_guardrails and llm_output_guardrails headers, so teams can test enforcement without modifying a model's default settings. announced · Sep 2026 · source · release history

example

  • Test Onyx guardrail enforcement on a single request without changing a model's default settings, by passing guardrail groups inline. { "llm_input_guardrails": ["onyx-guard/onyx-input"], "llm_output_guardrails": ["onyx-guard/onyx-output"] } announced · Sep 2026 · source
TrueFoundry AI Gateway integration shipped Connects Onyx's evaluate API to TrueFoundry's AI Gateway via an open-source guardrail wrapper, registering input and output endpoints so TrueFoundry can screen every prompt and response through Onyx. 1 release · 1 other source · first seen Sep 2026

release

  • Adds a TrueFoundry AI Gateway integration via an open-source guardrail wrapper that connects Onyx's evaluate API to TrueFoundry's custom-guardrail contract, registering /onyx-input and /onyx-output endpoints to screen prompts and responses.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history

example

  • Deploy the open-source guardrail wrapper so TrueFoundry's AI Gateway can call Onyx to screen every prompt and response. git clone https://github.com/truefoundry/integrations-custom-guardrails cd integrations-custom-guardrails/integrations/onyx cp .env.example .env # Set ONYX_API_KEY and WRAPPER_API_KEY in .env docker… announced · Sep 2026 · source
Agent-aware policy enforcement shipped Evaluates agent identity, permissions, session context, and the action being attempted at the tool-call boundary to block destructive operations, mask sensitive information, and restrict tools by policy. 1 release · first seen Oct 2026

release

  • Supports agent-aware enforcement beyond prompt inspection — evaluates agent identity, permissions, session context, and the action being attempted at the tool-call boundary, enabling Onyx to block destructive operations, mask sensitive information, and restrict tools by policy. announced · Oct 2026 · source · release history
Guardrail observability shipped Traces guardrail decisions as OpenTelemetry spans alongside latency and cost data, making them visible in existing observability stacks such as Grafana, Datadog, or Prometheus. 1 release · first seen Sep 2026

release

  • Guardrail decisions are traced as OpenTelemetry spans alongside latency and cost data, visible in existing stacks such as Grafana, Datadog, or Prometheus. announced · Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Onyx Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Onyx Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

2 entries

  1. October 20261
  2. September 20261

    2 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →