Onyx Security
commercialThe section your link pointed to isn't on Onyx Security's page any more, so we've brought you to the top.
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.
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 build -t onyx-guardrails-tfy .
docker run --rm -p 8000:8000 --env-file .env onyx-guardrails-tfy
{
"llm_input_guardrails": ["onyx-guard/onyx-input"],
"llm_output_guardrails": ["onyx-guard/onyx-output"]
}
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
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Releases
2 entries
No entries match these filters.
- October 20261
- September 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.