---
name: vet-third-party-ai-tool-packages-before
description: "Compare declared capabilities with actual files and probe risky servers. A bot reviews an AI tool package or server repository before adoption."
license: CC-BY-4.0
compatibility: "Needs access to: GitHub, Terminal, Docs."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-13"
  source: "https://botbento.com/usecases/vet-third-party-ai-tool-packages-before/"
  kind: workflow
  hermes:
    tags: ["security", "review", "installation", "automation", "risk"]
    category: ops
---
# Vet third-party AI tool packages before installation

Compare declared capabilities with actual files and probe risky servers.

## When to use

A bot reviews an AI tool package or server repository before adoption. It maps declared features and permissions, inspects files and configuration for mismatches, runs the server in a controlled probe where possible, and produces a plain-language risk report. Nothing is installed or connected until the user approves.

## Steps

1. When something happens: New tool package submitted
2. Inspect files and probe server
3. Risk report with approval gate

## Instructions

When a new package is submitted, read its declared capabilities and permissions. Compare them with the repository files and configuration. Run the server only in an isolated probe and record its observed behavior. Flag mismatches, unclear claims, and risky access. Write a short risk report with evidence and recommended next steps. Ask for approval before installing, connecting to tools, sending messages, making payments, or deleting anything.

## Source

Summarized in our own words from [USB: A trust layer for AI skills and MCP servers](https://news.ycombinator.com/item?id=50432661) (Hacker News, checked 2026-11-13). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/vet-third-party-ai-tool-packages-before/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
