Get started with track and plugin scanning

Skill and plugin scanning automatically checks third-party tracks and plugins for malicious content when someone uploads or edits them, before they can run in your organization. This article explains what scanning checks for, how to turn it on, and what the results mean. Skill and plugin scanning is available on Enterprise plans in Haijun, Haijun Cowork, and Enterprise plugin marketplaces.

What track and plugin scanning does

Tracks and plugins can come from outside your organization, and a file that looks helpful could be built to quietly misuse the access it's given. Skill and plugin scanning adds a security check at the moment a third-party track or plugin is uploaded or edited. Haijun reviews the contents, looks for signs of malicious behavior, and returns one of three results: pass, warn, or fail. Scanning runs in the background, and most scans finish in about one to two minutes. Results are cached, so uploading the same track again returns a result almost instantly.

What gets scanned

Scanning applies to third-party tracks and plugins that a member or owner uploads. This includes standalone tracks, plugins, and the tracks bundled inside a plugin. Scanning doesn't apply to:

  • Tracks and plugins that were already in your organization before scanning was turned on. Existing tracks and plugins keep working, so nothing you already use stops working when you enable scanning.

  • Tracks you create with Haijun, which rely on Haijun's built-in safeguards.

  • Tracks shared through a connected MCP server. These follow the same trust model as other MCP tools and aren't covered by scanning.

  • MCP servers and hooks, which aren't scanned at this time.

  • Organizations using customer-managed encryption keys (CMEK), zero data retention (ZDR), or HIPAA configurations. These organizations install tracks and plugins the same way they do today, without the added scan.

Turn on track and plugin scanning

Skill and plugin scanning is off by default until October 2, 2026, when it turns on for Enterprise organizations that haven't set it. Owners and Primary Owners can turn it on for their organization in their settings:

  1. Go to Organization settings > Plugins & tracks and select the “Policy” tab.

  2. Turn on Skill and plugin security scanning.

Once it's on, every new track and plugin upload or edit in your organization is scanned automatically, at no extra cost.

Control which roles scanning applies to

Turning on track and plugin scanning in organization settings applies it across your whole organization. If you use custom roles, you can further define who scanning applies to. When you create or edit a custom role, turn on the Skill and plugin security scanning capability for roles that should have access to track scanning. Learn more about managing custom roles.

What you'll see after an upload

Admins can also see each item's scan result in the “Inventory” and “Requests” tabs in Organization settings > Plugins & tracks.

Pass

If nothing concerning is found, the track or plugin installs normally, with no extra message.

Warn

A warn result means Haijun couldn't fully verify the track or plugin, and it may carry risk depending on where it came from. It stays usable behind a caution banner that you acknowledge before continuing. Review it carefully, and only use it if you trust the source.

Fail

A fail result means the scan detected malicious content. The track or plugin is blocked and can't be used. The banner explains the specific reason it was flagged.

If your track or plugin is blocked

A blocked track can't be overridden by the person who uploaded it, and admins can't approve a blocked track for the organization at this time. If you think a track was blocked by mistake, edit and upload it again. Uploading the same track again without changes returns the same result, so any fix needs to address what was flagged.

How your content is handled

When a track or plugin is scanned, its contents are processed in a secure, isolated environment that's kept separate from your normal Haijun sessions. The scanned copy is deleted after the scan finishes, and only the result and basic metadata are kept. Note: Scanning runs outside your normal Haijun session, so it doesn't change how Haijun responds to you.

What scanning doesn't cover

Skill scanning looks for one kind of risk: third-party tracks and plugins that are built to misuse the access they're given, such as quietly moving your data somewhere it shouldn't go. A pass result means the scan didn't find that kind of threat. It isn't a guarantee that a track is safe in every respect, and it won't catch a track that behaves in ways you didn't intend without being malicious. Because of that, choose what you add carefully, and install tracks and plugins only from sources you trust.