Skip to main content

​
Inventory View

Use inventory to quickly understand the AI agent footprint on an endpoint: installed runtimes, MCP servers, local config files, telemetry hooks, OTLP settings, and recent observed activity. 
beacon endpoint inventory
beacon endpoint inventory --json
beacon endpoint inventory --all
Use --system for packaged or MDM-managed installs: 
sudo beacon endpoint inventory --system --all

​
Key Questions

  • Which supported agent runtimes are installed or configured on this machine?
  • Which MCP servers are referenced by local agent configuration?
  • Which runtime config files can Beacon inspect locally?
  • Which hooks, OTLP settings, or launch environment entries are present?
  • Which detected runtimes have recently produced Beacon events?

​
What To Look For

SignalWhy it matters
Installed runtimesShows the local AI tools present on the endpoint.
Config filesIdentifies where runtime behavior and integrations are defined.
MCP serversShows external tools an agent may be able to call.
Hooks and OTLP settingsConfirms whether Beacon can collect telemetry.
Managed stateDistinguishes Beacon-managed collection from customer-managed config.
Observed eventsConfirms the runtime has recently emitted Beacon telemetry.
Inventory reads local endpoint state only. It does not authenticate to remote SaaS accounts or MCP servers.

​
Runtime Coverage States

  • Installed: the runtime or executable appears to be present locally.
  • Configured: Beacon can see telemetry settings, hooks, launch environment entries, or other local config for the runtime.
  • Managed: the detected telemetry surface appears to be configured by Beacon.
  • Observed: recent Beacon events in the runtime log reference the runtime.
A runtime can be installed but not configured, configured but not observed, or observed only in a different user-mode or system-mode log.

​
MCP Servers And Configs

Use MCP inventory to spot tool exposure from local agent configs:
  • Expected MCP servers missing after deployment
  • Unexpected MCP servers on sensitive endpoints
  • Server references introduced by a specific runtime config
  • User-mode versus system-mode config differences

​
Dashboard Inventory

Open the dashboard for a quick visual check alongside top harnesses, models, repositories, MCP servers, and risk signals: 
beacon endpoint dashboard --open

​
Investigation Paths

​
Validate rollout

Confirm service health, runtime coverage, and visible activity: 
beacon endpoint status
beacon endpoint inventory
beacon endpoint dashboard --open

​
Audit MCP exposure

Export complete local state for review or fleet comparison: 
beacon endpoint inventory --all
beacon endpoint inventory --json

​
Troubleshoot missing telemetry

Check whether:
  • The runtime is installed on the endpoint
  • Beacon can detect the runtime or its configuration file
  • The MCP server is defined in a supported local config path
  • Hooks, OTLP settings, or launch environment entries are configured for that runtime
  • User mode or system mode is reading the config and runtime log you expect
  • Recent events exist in the active runtime log or a rotated archive

Use Cases

Review common Beacon workflows for local agent runtime visibility.

Agent Runtime Telemetry

Collect, inspect, and forward normalized telemetry from local agent runtimes.

beacon endpoint dashboard

Open the local dashboard and review Security Overview.

beacon endpoint inventory

Review flags, examples, and JSON output behavior.

Endpoint discover

Discover supported local agent harnesses and telemetry state.

Data inventory

Review runtime coverage and endpoint event fields Beacon can write.