PAGES
← all tools
◆ AI Security Posture & Discovery

WitnessAI

MCP authentication and authorization: OAuth for AI agents (2026-09-28) commercial

WitnessAI sits in the network path and monitors, controls and protects employee, application and agent AI activity.

Summary

WitnessAI is a commercial AI security tool that monitors, controls, and protects employee, application, and agent AI activity as it passes through the network path. It operates as a service and is designed for governance of AI usage, fitting into the ai-governance category. Its documentation positions it alongside other network visibility tools. The product was launched in 2023.

WitnessAI sits in the network path and monitors, controls and protects employee, application and agent AI activity.

How WitnessAI helps

Which AI tools and MCP connections are actually in use across the network, including ones nobody registered?

scans network-level traffic for AI application signatures and MCP connections, cataloging thousands of applications — including native apps like Windows Copilot and Microsoft 365 — and ties each captured action back to the human identity behind it, all without installing endpoint clients or browser extensions

Which employees or agents sent sensitive data to an external model, and what did the model send back?

keeps auditable records of prompts, uploads, and responses routed through the network path, showing who sent what to which model and what came back, usable as evidence in AI risk reviews under frameworks such as DORA and the EU AI Act

Which agent tool calls should never have been allowed to run?

checks agent and tool-call activity against an approved-tool and MCP allow-list before execution, blocking unauthorized calls and keeping an audit trail of governed activity across more than 100 LLM types

Can a sensitive value like a customer's SSN leave the building through a prompt?

tokenizes classified sensitive values before a prompt leaves the enterprise, then restores the original value only in responses to users authorized for policy-enforced detokenization

Would this query have been flagged if it were phrased differently?

classifies conversational intent and context with machine learning rather than keyword or regex matching, so paraphrased or indirect attempts to expose sensitive data or violate policy still surface, each with a confidence score adjusted by contextual signals

Should a given query have gone to an external model at all?

routes queries carrying classified sensitive intent, such as non-public drug research or financial data, away from external models to approved internal ones automatically

all 5 features, with the evidence for each →

Languages

Not documented

Features

5 capabilities

Built from WitnessAI'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 WitnessAI offers you

  • Administrative audit log2
  • Agentless deployment1
  • ML-based detection1
All capabilities 5 capabilities
Agentic Control shipped Enforces approved-tool and MCP allow-lists, blocks unauthorized tool calls, performs pre-execution checks, applies runtime controls to agent activity, and maintains a full audit trail of governed agent interactions. 3 releases · first seen Sep 2026

Also counts toward: Administrative audit log

release

  • Adds an organization-wide approved-tool list for MCP servers and tools, enforced at the network level before agent calls execute across IDE, chat, and agent surfaces via Agentic Control.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ MCP authentication and authorization: OAuth for AI agents (2026-09-28) · Sep 2026 · source · release history
  • Adds routing action within Control to redirect sensitive queries (such as non-public drug research or financial data) from external models to approved internal models based on classified intent. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
  • Adds Agentic Control to enforce approved-tool and MCP allow-lists, block unauthorized tool calls before execution, perform pre-execution checks on approved tool calls, apply runtime controls to agent activity, and maintain a full audit trail of governed agent and tool-call activity across more than 100 LLM types. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
AI Data Protection shipped Applies runtime guardrails to inspect and filter harmful or off-policy responses, combined with data tokenization and detokenization to protect sensitive values like PII during AI interactions. 3 releases · first seen Sep 2026

release

  • Adds bidirectional content inspection via the Protect module's runtime APIs, evaluating agent inputs before processing and responses before delivery, with malicious prompt detection validated in production across more than 100 LLMs. MCP authentication and authorization: OAuth for AI agents (2026-09-28) · Sep 2026 · source · release history
  • Adds Protect runtime guardrails to inspect prompts and filter harmful or off-policy responses in AI interactions routed through the platform, covering both inputs and generated outputs for PII and sensitive data per NIST Generative AI Profile guidance. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
  • Adds data tokenization that replaces classified sensitive values (such as SSNs) before prompts leave the enterprise and policy-enforced detokenization that restores original values for authorized users in model responses. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
AI Traffic Control Policies shipped Enforces four-tier intelligent policies (allow, warn, block, route) on AI traffic using intent-based machine learning classification to evaluate conversational context and purpose. 3 releases · first seen Sep 2026

Also counts toward: ML-based detection

release

  • Supports intent-based machine learning classification of conversational context to drive Control module enforcement decisions: allow, warn, block, or route to an approved internal model. MCP authentication and authorization: OAuth for AI agents (2026-09-28) · Sep 2026 · source · release history
  • Adds Control capabilities to enforce four-tier intelligent policies — allow, warn, block, and route — on AI traffic routed through the platform, enabling proportionate enforcement over prompt, upload, response, and tool-call interactions. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
  • Adds intent-based machine learning classification that evaluates conversational context and purpose to detect sensitive data, suspicious behavior, and policy violations that keyword and regex matching cannot represent, with confidence scores adjusted by contextual signals. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
AI Compliance Auditing shipped Produces auditable records of employee and agent interactions with AI models to support risk reviews under frameworks such as DORA and the EU AI Act. 2 releases · first seen Sep 2026

Also counts toward: Administrative audit log

release

  • Adds unified audit trails that correlate agent actions and blocked tool calls to a triggering human identity, covering both agent and employee activity routed through the platform. MCP authentication and authorization: OAuth for AI agents (2026-09-28) · Sep 2026 · source · release history
  • Produces auditable records of what employees and agents sent to which model and what came back, providing evidence for AI risk reviews under frameworks such as DORA and the EU AI Act. AI data classification: how it works (2026-09-13) · Sep 2026 · source · release history
AI Discovery and Visibility shipped Discovers AI tools, MCP connections, and agent actions at the network level to catalog applications and attribute activities to human identities without requiring endpoint clients. 2 releases · first seen Sep 2026

Also counts toward: Agentless deployment

release

  • Adds MCP server and tool visibility through the Observe module, identifying agentic sessions by inspecting tool advertisements in traffic payloads across Claude Desktop, VS Code with AI extensions, and local agents built on LangChain, LlamaIndex, CrewAI, and custom code. MCP authentication and authorization: OAuth for AI agents (2026-09-28) · Sep 2026 · source · release history
  • Adds Observe module for network-level discovery of AI tools and MCP connections — including native apps like Windows Copilot and Microsoft 365 — cataloging thousands of AI applications without endpoint clients or browser extensions, and attributing captured agent actions to a human identity.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ AI data classification: how it works (2026-09-13) · 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 WitnessAI, 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 WitnessAI 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 →

Website history

witness.ai, every change

WitnessAI's home page and 18 more pages as they looked each month from May 2024 to October 2026: 101 renders, 19 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

2 entries

  1. September 20262

    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 →