Assets

The Assets page is your inventory of dependencies. An asset is one of the things your agents rely on to do their work: a model, an MCP server, or a tool. Switch Trust fills this inventory from code scans and from the guardrails your agents run behind, so one risky dependency shared across several agents is visible in one place.

​

Browse by asset type

Select Assets in the left navigation, then switch between the Models, MCP servers, and Tools tabs. The count beside each tab is how many of that asset type Switch Trust has found. Each tab is a searchable table of that asset type, and every one carries Highest severity and Issues, so you can see which dependencies carry the most risk. A dependency shared across several agents appears once here, and its Used by list, in the detail panel, names the agents that rely on it. To triage the findings those columns point to, see Discovery results. Each table opens on a default set of columns. Select the column control, next to the result count, to change which columns are shown. Whatever a table leaves out, the asset’s full profile is in its detail panel.

​

Models

The Models tab lists the models your agents call. By default it shows: Model health is an evaluation result, not a discovery finding, so a model that hasn’t been evaluated shows a dash here even when it carries issues. For how the score is calculated and what each band means, see Evaluation results.

​

MCP servers

The MCP servers tab lists the Model Context Protocol servers your agents connect to. By default it shows:

​

Tools

The Tools tab lists the individual tools your agents can call. By default it shows:

​

The asset detail panel

Select any asset to open its detail panel. The panel is headed by the asset type (Model, MCP Server, or Tool) and its name, and opens on Overview, with Issues and Locations beside it, and an Evaluations tab for models.

• Overview - What the asset is and where it’s used
• Issues - The findings open against this asset, with Name, Severity, and Occurrences. Expand a finding to list the places it occurs, then select one to open its Occurrence details with the full record, down to the line of code that triggered it. See Discovery results
• Locations - The files the asset was found in, across every agent that uses it, shown as a count of locations across agents. Select Show on a location to see the code in place
• Evaluations - For a model, the individual probes behind its health score. See Evaluation results

​

Overview

The Overview tab opens with an Insights section:

• Highest severity - The most serious open issue, with the issue count beside it
• Locations - The file where the asset turned up, with a note of how many other locations there are. The full list is under the Locations tab
• Used by - The agents that depend on it, or a dash when none do

A model also shows a Model health score card with the overall score, its band, and category scores for Jailbreaks, Misuse, Toxicity, Security, and Robustness. Bands run from Excellent down through Good, Fair, and Poor, to Very Poor. For how the score is calculated, see Evaluation results. A Details card carries the asset’s profile, with a dash for any field that doesn’t apply. What it holds depends on the asset type:

• Model - Name, Manufacturer, Task, Base model, Size, Downloads, License, Deprecation type, Suggested replacement, Deprecation date, Last seen, and Created at
• MCP Server - Name, Manufacturer, Type, Supplier, Library, License, Auth required, Last seen, and Created at
• Tool - Name, Description, Sources (Scan or Guardrails), Last seen, and Created at

For a tool, a Code snippet section below the details shows the tool’s implementation where the code is available.

​

Next steps