AI agent visibility

Your network is full of
AI agents you didn’t deploy.

Viskor finds, explains and controls every use of AI on your network: people chatting with AI, programs calling AI APIs and autonomous agents using tools. It shows what each one touches, who is behind it, and what changed. No endpoint agents required, and no changes to your stack.

NO ENDPOINT AGENTS REQUIREDANY CLOUD OR ON-PREMISESMCP & TOOL-CALL AWAREIDENTITY ATTRIBUTIONEU AI ACT READY
Full‑Spectrumcoverage of AI traffic: network, browser and your existing logs
Deepbehaviour detection, each check comparing activity with its own history
Real-timeblocking, with policy changes applied live and no restart
1place for inventory, identity, control and audit evidence
The problem

AI is already inside
your network perimeter.

Developers, analysts and power users all run AI: Copilots, custom LLM workflows, autonomous coding agents, MCP tool servers. Most security teams cannot see what is calling out, to whom, or on whose behalf.

No AI traffic visibility

SIEM and firewall rules weren't written for LLM endpoints. Agent calls blend in with ordinary web traffic.

Data exfiltration risk

Agents send code, documents and emails to outside models, and prompt injection can make them do it on an attacker's behalf.

No user attribution

Raw IP logs don't map back to people, teams or business context, and agents have no owner at all.

Policy and regulatory gaps

Approved tools change weekly, blanket bans push AI underground, and regulators now ask for an inventory and evidence.

How it works

From raw traffic to
a decision you can defend.

Collect

DNS, proxy, browser extension and your existing logs and traces each see a different part of AI traffic.

Score

Every event gets a provider, a confidence that it is AI, and a separate confidence that it is an agent at work.

Attribute

DHCP and LDAP / Active Directory turn addresses into a person, department and computer.

Decide

Policies allow, alert or block, with alerts delivered to your SIEM, chat or ticketing tools.

Learn

Behaviour detection compares each person, agent and department with its own history and raises Findings.

What you get

See every AI agent.
Know who’s behind it.

Everything a security team needs to discover, understand, control and evidence AI use, in one portal.

DNS sensor

Shows which AI services every device looks up. Covers every app with no content inspection, and can block lookups.

AI-aware proxy

Sees the requests themselves: model, tokens, tool calls and agent names. Enforces block decisions and rate limits.

Optional browser extension

Records AI web chats in ChatGPT, Claude, Gemini, Copilot and Perplexity. It sends usage details only, never the text of prompts or replies.

Source integrations

Reuse the resolver, firewall and gateway logs (syslog or HTTPS) and OpenTelemetry traces you already collect. No new sensors needed.

No-code log formats

Add any product with a JSON format definition and a few sample lines, tested before you save.

Internal AI services

Declare self-hosted models and gateways (Ollama, vLLM, your own) so their traffic is recognised by name, even when encrypted.

Flight Recorder

Every AI event with full detail, and a plain-language explanation of why it counts as AI or agent activity.

Sessions

Events grouped into conversations and agent runs, with a timeline of every model and tool call in order.

Identity attribution

DHCP and LDAP / AD sources and an IP user map put a person, department and computer behind every address.

Policies

Allow, alert or block by provider, model, MCP tool, subnet, confidence or risk, with a custom block message and token rate limits.

Alert delivery

Signed webhooks send policy alerts and behaviour findings to your SIEM, chat or ticketing system, filtered by risk and severity.

Detection depth you choose

Advanced Agent Detection, internal (east-west) traffic observation and optional internal TLS decryption, each switched on independently.

Built for how agents really work

Not just where they connect.
What they do.

  • 01

    Recognises the client

    Claude Code, Codex, OpenAI SDKs, browsers and more, identified from the software. Agents can also name themselves with a header.

  • 02

    Follows MCP tool calls

    See which Model Context Protocol tools an agent called, in order, inside each session.

  • 03

    Separates AI from agents

    Two confidence scores: is this AI, and is it an agent at work (tool use, MCP, machine-speed loops)?

  • 04

    Says what it couldn't see

    Every event records what the sensor could observe (connection, headers or body), so gaps are explicit.

viskor · live activity
Operatorj.patel · Pricing
Operatorci-runner-04
Agentpricing-helper
Brainsanthropic · claude
Hands · send outsend_email
Hands · read datapolicy_db.query
Reachquote-agent → billing
EXPOSURE CHAIN
Untrusted input + private data + a way to send out. All three together is the riskiest shape for an agent.
Agent governance

Name, own and govern
every agent.

  • 01

    Agent inventory

    Every AI client and agent, with its providers and activity. Duplicate identities are suggested for merging.

  • 02

    Owners and labels

    Assign an accountable owner and a friendly name. Network identity suggests a likely owner.

  • 03

    Brains, hands and reach

    See the models an agent uses, the tools it calls (grouped by what they do) and the agents and servers it reaches, including a second hop.

  • 04

    Communication graph

    A live map and Sankey view of agents, providers, MCP servers and internal hosts, including agent-to-agent links with confidence scores.

Behaviour detection

Rules catch what you expected.
Findings catch what changed.

A wide set of detectors compare each person, department, agent and computer with its own history after a learning period. Acknowledge, dismiss or suppress a finding, or put someone on a watchlist so stricter policies apply.

New and unusual

First use of a provider

A person or team uses an AI service for the first time.

New agent appeared

An agent identity never seen before.

New model for an agent

An agent switches to a model it has never used.

New MCP tool or server

An agent picks up a tool or server it has never used.

Dormant agent returned

Active again after 30 or more days of silence.

Unknown AI from a host

A computer starts talking to an AI service nobody recognises.

Outside usual hours

Activity at an hour or on a day they never use.

Agent used by someone new

An owned agent run by a different person.

Volume and cost

Token volume spike

At least three times a typical day's tokens.

Upload volume spike

Far more data sent to AI than usual.

Organisation-wide spike

Everyone together, even when no one person stands out.

Steady growth

Usage doubled compared with a month ago.

Runaway agent session

A session ten times its usual size: a loop that won't stop.

Attack patterns

Sensitive read, then sent out

Reads private data or runs code, then sends something out within 30 minutes.

External model reaches a sensitive host

An outside model gets to a sensitive internal server through another agent.

New internal connection

An agent talks to another agent or server for the first time.

Burst of internal connections

Many new internal destinations in a day: the shape of lateral movement.

Scan spread across agents

Several agents together reaching places nobody reached before.

Blocked, then got through

Reached the provider another way, or switched provider, within 15 minutes of a block.

Traffic turned automated

A person's account starts behaving like an agent.

Dashboards

One picture for the board.
One queue for the team.

Overview

An activity map of departments and their agents, with stat cards, trends and breakdowns. Click to zoom in, or press Present for a big screen.

48312317agents activepeople using AIhigh-risk findingsAI providers

Executive

Four headline numbers and the activity map, with no tables and no jargon. Made for senior audiences.

Operations

An action queue: high-risk findings, new agents, agents with no owner, quiet data sources and recent blocks, with one-click actions.

Viskor Brain

Everything Viskor knows as an interactive 3D globe of people, agents, models, tools and findings, joined by their real relationships.

Compliance

Evidence for the auditor,
not just a policy document.

A compliance module aligned with the EU AI Act turns observed AI use into the inventory, risk view and decision record that regulators and auditors ask for.

  • 01

    Usage register

    Which AI providers each department uses, with users, events and risk tier. Rebuilt nightly, and exportable.

  • 02

    Provider classifications

    Your own risk tier, GPAI flag and regulatory tags for each provider, with a written rationale and full history.

  • 03

    Incident review

    Viskor flags possible incidents but never escalates on its own. A person decides, with a note, and every decision is logged.

  • 04

    Audit packs and audit log

    CSV evidence for any period, and a record of who changed what in the portal.

ProviderDepartmentTier
AnthropicEngineeringLimited
OpenAIFinanceLimited
Internal · acme-llmPricingHigh
PerplexityMarketingMinimal
Unknown · 10.0.4.82UnattributedUnclassified
Deploy anywhere

Built for security teams.
Runs wherever you do.

Viskor serves organisations worldwide. Run it on any cloud infrastructure or in your own data centre, so you choose where your data lives. You get deep visibility without friction: nothing to install on endpoints and nothing to re-architect. Every operator has their own account, and every change is audited.

Any cloud or your own data centre
No endpoint agents required
Agent & MCP tool-call aware
Prompt text never collected by the extension
Revocable device & source tokens
Full audit log
Demos

See it work, in a few minutes.

Interactive walk-throughs of the portal. They run in your browser on illustrative example data.

Early access

Name and govern every
AI agent on your network.

Viskor gives every AI agent a stable identity, a named owner and an audit trail. Shadow AI becomes something you can govern, not just watch. We're onboarding a small group of security and identity teams for early access.

✓  Request received — we'll be in touch shortly.

We use your email only to contact you about Viskor early access. It is never shared, and we don't send spam. Ask us to delete your details at any time: hello@viskor.ai.