Skip to content
NewWatch the two minute introduction to EndLayerWatch now →
The Guardian Agent Platform

Layer 1: the guardian agents on every device.

The device layer of the Guardian Agent Platform.

Guardian agents that find shadow AI, connect tools to their accounts and access, and enforce your policy on supported AI requests where the work happens.

On-device decisionsNo language model requiredOne console for your fleet
Inside the endpoint

Before the request
leaves the machine.

Follow a supported AI interaction from local discovery to an enforceable decision. Scroll to explore, or select a step.

Layer 1 / Device boundary
A request moving through the Layer 1 AgentLocal apps, coding agents and MCP connections feed an on-device policy check. Supported requests can be allowed, warned, redacted or blocked. Redacted evidence is reported to the console. AI APPSAGENTSMCP ENDLAYER LOCAL POLICY CHECKRequest / promptSecret value detectedCHECK BEFORE SENDINGDECISION RECORDActionBLOCKPolicy version retainedSecret value removedREADY TO REPORT → ALLOW!WARN / REDACTBLOCK
01 / DiscoverA coding agent is found.
Tool · account · declared MCP access
Local check → decision → evidence
01 / Surface

Find the AI you weren’t told about.

Read supported local signals to find AI apps, coding agents, local models and MCP connections. Discovery needs no per-tool API integration, traffic interception or execution of the tools it finds.

  • See work, personal or unknown account context.
  • Identify credential presence without reporting the secret.
  • Connect tools to declared repositories and MCP access.
Explore the 21 signals ↗
02 / Monitor

Inspect where the request begins.

For supported enforcement paths, a local TLS gateway reads the request on the device and re-encrypts forwarded traffic. Policy checks use deterministic rules and trained classifiers, with no language model required.

  • Check prompts for sensitive content before sending.
  • Evaluate the interaction against your published rules.
  • Keep local inspection separate from conversation collection.
Understand the data boundary ↓
03 / Govern

Make the policy a decision.

Let approved work continue. Warn, redact or block supported interactions when a rule applies. The action follows the policy your organisation publishes.

✓ Allow! Warn / redact× Block

Request controls are distinct from stopping an application or removing it. App removal needs an administrator; coverage depends on the tool and operating system.

04 / Evidence

Keep the reason behind the result.

Build a versioned, redacted record on the endpoint. Evidence is saved locally, then delivered through an encrypted outbound route to the platform.

  • Link the decision to the policy version behind it.
  • Give teams reviewable findings and evidence for audits.
  • Retain unknown results when a check cannot complete.

Framework mappings support control reviews; they do not establish certification or guarantee compliance.

Follow the evidence ↗
Agent + platform

Local control. Company-wide context.

The agent observes AI use and applies supported controls on the endpoint. Your teams manage policy and investigate the evidence in one console.

On the device

Observe and enforce.

Discover supported AI, evaluate local interactions and produce redacted evidence. Local discovery can continue offline.

DiscoverInspectAct
In the console

Investigate and govern.

Attribute available usage and spend to tools, people and projects. Publish policies, assign findings and use the evidence to review AI value alongside business outcomes.

InventoryPolicyEvidence
Start with your endpointsmacOS · Windows · LinuxReview environment coverage ↗
Installation & rollout

One device first.
Your fleet when ready.

Validate the signals and controls on your own workflows, then use your existing device management to roll out the agent.

01

Connect a pilot.

Install the agent on a supported device. Enrol with a claim code that an authorised user claims in the console.

Device→ claim code →Console
No shared fleet secret needed for this path.
02

Validate the behaviour.

Review the first inventory, confirm data collection and test policy actions against the tools your people use.

Signals→ review →Policy
Confirm tool coverage and measure device impact.
03

Deploy with your MDM.

Distribute through Intune, Jamf or SCCM. Unattended enrolment exchanges an organisation fleet secret for a device credential.

MDM→ enrol →Fleet
Each enrolled device gets its own credential.
Agree before fleet rollout
AccessOS permissions & certificate setupCompatibilityYour AI tools & security stackLifecycleUpdates, rollback & removal

Choose the current package and configuration for your environment.

View installation options ↗
Security & data handling

Clear boundaries.
Before you deploy.

Discovery, request inspection and evidence reporting serve different purposes. Here is how the data is handled at each step.

On the endpoint

Inspect locally.
Minimise before reporting.

Local signalsSupported request checksSecret-value removal
Encrypted
outbound route
In the platform

Redacted evidence. Traceable decisions.

InventoryPolicy versionFindings

Keys: presence, not values.

Discovery reports that a credential exists. Secret values are removed on the endpoint before evidence is built.

Repository context, not code.

Discovery identifies repository context and bounded file inventory. It does not collect source-code contents.

Conversations are opt-in.

Prompt, response and transcript collection is off by default. Administrator-enabled collection is distinct from local inspection for enforcement.

Rules, not an LLM judge.

Local decisions use deterministic rules and trained classifiers. Your request is not sent to a language model to make that decision.

Inspect the published collection schema ↗
Built for operation

Keep control
as the fleet changes.

A rollout is more than an install. Reporting state, policy versions and evidence delivery need to remain visible.

01 / Policy

Change the rule centrally.

Publish a new policy version from the platform. Keep earlier decisions tied to the version that produced them.

02 / Reliability

A failed check stays unknown.

One failed collection check does not stop the scan. Missing evidence is not presented as a pass.

03 / Delivery

Save first. Send next.

Local discovery continues offline and evidence is saved before delivery. The console shows the last reported state, including paused or silent devices.

A few practical details

Plan your pilot.

Confirm the deployment-specific details with your team before expanding to the fleet.

What should we measure in the pilot?

Measure CPU, memory, scan time and request latency on representative devices and workflows. Resource use depends on your configuration and enabled controls; agree acceptance criteria before expanding.

How does enforcement behave offline?

Offline discovery and local evidence storage are covered above. For request enforcement, confirm cached-policy behaviour, fail-open or fail-closed settings and queue limits for the paths you enable.

Can we explore the collection approach first?

The separate open-source Surface tool lets you inspect AI activity on a machine. It is not the managed Layer 1 Agent or the full platform. Explore open-source Surface ↗.

EndLayer

Give AI room to work.And clear boundaries.

See the Guardian Agent Platform on your own fleet. Find every AI tool, understand what it reaches and costs, and apply the controls your team needs.

One connected layer of control
Devices · Cloud · ApplicationsSurface / Monitor / Govern