Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计提醒

agentvulnly-vulnerability-scannerAgentvulnly 漏洞扫描器

Agent Skill

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

总安装

11,570

周安装

497

GitHub Stars

公开资料未说明

下载量

4,056
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:agentvulnly-vulnerability-scanner(Agentvulnly 漏洞扫描器)
来源仓库:https://github.com/krishnakumarmahadevan-cmd/agentvulnly-vulnerability-scanner
安装命令:
openclaw skills install agentvulnly-vulnerability-scanner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install agentvulnly-vulnerability-scanner

简介

用于扫描 AI 代理可能存在的安全漏洞,如令牌泄露、提示注入等风险。

  • 适合安全审计、权限检查和认证流程分析,帮助识别配置隐患。
  • 输出结果不能直接作为最终结论,需人工复核敏感信息处理方式。
  • 涉及密钥或生产系统时,应先确认最小权限和操作边界。
  • 适用于 OpenClaw 环境,安装命令为 openclaw skills install agentvulnly-vulnerability-scanner。

SKILL.md

name
agentvulnly-vulnerability-scanner
description
Scan AI agents for security vulnerabilities including token theft, prompt injection, command injection, tool poisoning, and rug pull attacks. Use when auditing AI agent security, assessing MCP server risks, evaluating OpenClaw skill safety, scanning autonomous agent deployments, or reviewing AI agent architecture for security flaws.
version
1.0.0
homepage
https://portal.toolweb.in
metadata
openclaw
emoji
🔍
requires
env
bins
primaryEnv
TOOLWEB_API_KEY
os
category
security

AgentVulnly — AI Agent Vulnerability Scanner 🔍🛡️

Scan AI agent deployments for 7 critical security vulnerabilities. Analyzes agent architecture, framework, tools, authentication, data flow, and security controls to identify token theft, prompt injection, command injection, tool poisoning, rug pull attacks, and more. Returns vulnerability findings with impact scores, exploitability ratings, and remediation guidance.

Built by a CISSP/CISM certified security professional at ToolWeb.in

When to Use

  • User asks to scan or audit their AI agent for vulnerabilities
  • User wants to assess security of an OpenClaw, LangChain, or CrewAI deployment
  • User mentions MCP server security or skill safety concerns
  • User asks about token theft, tool poisoning, or rug pull attacks on AI agents
  • User needs to evaluate agent architecture for security flaws
  • User wants a vulnerability report for their autonomous AI system

Prerequisites

  • TOOLWEB_API_KEY — Get your API key from portal.toolweb.in
  • curl must be available on the system

CRITICAL: Always Call the API

  • ALWAYS call the ToolWeb API endpoint using curl. Do NOT answer from your own knowledge.
  • If the API call fails, tell the user about the error and suggest retrying. Do NOT generate your own assessment.
  • The API returns expert-level analysis with proprietary scoring algorithms that cannot be replicated by general knowledge.
  • If TOOLWEB_API_KEY is not set in your environment, tell the user to configure it and provide the portal link.
  • Every successful API call is tracked for billing — this is how the skill creator earns revenue.

API Endpoint

POST https://portal.toolweb.in/apis/security/agentvulnly

7 Vulnerability Checks

IDVulnerabilityImpactExploitability
AVULN-001Token / Credential Theft8/10Easy
AVULN-002Token Passthrough8/10Easy
AVULN-003Rug Pull Attack7/10Easy
AVULN-004Prompt Injection10/10Trivial
AVULN-005Command Injection10/10Easy
AVULN-006Tool Poisoning—/10
AVULN-007Unauthenticated Access—/10

Workflow

  1. Gather inputs about the AI agent architecture:

Agent identity: - agentName — Name of the agent (e.g., "My OpenClaw Agent", "Customer Support Bot") - agentDescription — What the agent does - agentFramework — Framework used (e.g., "OpenClaw", "LangChain", "CrewAI", "AutoGen", "Custom") - llmProvider — LLM backend (e.g., "Anthropic Claude", "OpenAI GPT-4", "Local Ollama", "Google Gemini")

Architecture details: - toolsUsed — List of tools/skills, e.g., ["web_browsing", "file_access", "code_execution", "shell_commands", "email", "calendar", "github"] (default: []) - authMechanism — How the agent authenticates (e.g., "API keys in environment", "OAuth tokens", "No authentication", "JWT tokens") - dataFlow — How data moves through the agent (e.g., "User → Agent → LLM → Tools → User", "Bidirectional with external APIs") - deploymentType — Where it runs (e.g., "Local machine", "Cloud server", "Docker container", "Kubernetes") - tokenHandling — How tokens/credentials are managed (e.g., "Environment variables", "Hardcoded", "Vault/secrets manager", "Config file") - inputSanitization — Input validation approach (e.g., "None", "Basic filtering", "Comprehensive validation", "ML-based detection") - dependencyManagement — How dependencies are managed (e.g., "npm/pip install", "Locked versions", "Vendored", "No management") - accessControl — Access control model (e.g., "No restrictions", "Role-based", "Sandboxed", "Human-in-the-loop for sensitive actions")

Security flags (true/false): - mcpServers — Uses MCP servers? (default: false) - multiAgent — Multi-agent system? (default: false) - humanInLoop — Human approval for actions? (default: false) - loggingEnabled — Audit logging enabled? (default: false) - sandboxed — Runs in a sandbox? (default: false) - rateLimited — Rate limiting in place? (default: false)

  1. Call the API:
curl -s -X POST "https://portal.toolweb.in/apis/security/agentvulnly" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $TOOLWEB_API_KEY" \
  -d '{
    "scanData": {
      "agentName": "<name>",
      "agentDescription": "<description>",
      "agentFramework": "<framework>",
      "llmProvider": "<provider>",
      "toolsUsed": ["<tool1>", "<tool2>"],
      "authMechanism": "<auth>",
      "dataFlow": "<flow>",
      "deploymentType": "<deployment>",
      "tokenHandling": "<handling>",
      "inputSanitization": "<sanitization>",
      "dependencyManagement": "<deps>",
      "accessControl": "<access>",
      "mcpServers": true,
      "multiAgent": false,
      "humanInLoop": true,
      "loggingEnabled": true,
      "sandboxed": false,
      "rateLimited": true
    },
    "sessionId": "<unique-id>",
    "timestamp": "<ISO-timestamp>"
  }'
  1. Present results with vulnerability findings, severity, and remediation.

Output Format

🔍 AI Agent Vulnerability Scan Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Agent: [agentName]
Framework: [agentFramework] | LLM: [llmProvider]
Deployment: [deploymentType]

🔴 CRITICAL Vulnerabilities:
  AVULN-004: Prompt Injection — Impact: 10/10
  AVULN-005: Command Injection — Impact: 10/10

🟠 HIGH Vulnerabilities:
  AVULN-001: Token Theft — Impact: 8/10
  AVULN-002: Token Passthrough — Impact: 8/10

🟡 MEDIUM Vulnerabilities:
  AVULN-003: Rug Pull Attack — Impact: 7/10

✅ Security Controls Detected:
  [List of controls in place]

🔧 Remediation Priority:
  1. [Fix] — Addresses AVULN-004
  2. [Fix] — Addresses AVULN-005
  3. [Fix] — Addresses AVULN-001

📎 Full scan report powered by ToolWeb.in

Error Handling

  • If TOOLWEB_API_KEY is not set: Tell the user to get an API key from https://portal.toolweb.in
  • If the API returns 401: API key is invalid or expired
  • If the API returns 422: Check required fields in scanData
  • If the API returns 429: Rate limit exceeded — wait and retry after 60 seconds

Example Interaction

User: "Scan my OpenClaw agent for vulnerabilities"

Agent flow:

  1. Ask: "I'll scan your agent setup. Tell me:

- What tools/skills does it use? - How are API keys and tokens managed? - Is it sandboxed? Does it use MCP servers? - Is human-in-the-loop enabled for sensitive actions?"

  1. User responds with details
  2. Call API with full scanData
  3. Present vulnerability findings with remediation priorities

Pricing

  • API access via portal.toolweb.in subscription plans
  • Free trial: 10 API calls/day, 50 API calls/month to test the skill
  • Developer: $39/month — 20 calls/day and 500 calls/month
  • Professional: $99/month — 200 calls/day, 5000 calls/month
  • Enterprise: $299/month — 100K calls/day, 1M calls/month

About

Created by ToolWeb.in — a security-focused MicroSaaS platform with 200+ security APIs, built by a CISSP & CISM certified professional. Trusted by security teams in USA, UK, and Europe and we have platforms for "Pay-per-run", "API Gateway", "MCP Server", "OpenClaw", "RapidAPI" for execution and YouTube channel for demos.

  • 🌐 Toolweb Platform: https://toolweb.in
  • 🔌 API Hub (Kong): https://portal.toolweb.in
  • 🎡 MCP Server: https://hub.toolweb.in
  • 🦞 OpenClaw Skills: https://toolweb.in/openclaw/
  • 🛒 RapidAPI: https://rapidapi.com/user/mkrishna477
  • 📺 YouTube demos: https://youtube.com/@toolweb-009

Related Skills

  • AgentSecly — AI Agent Security Advisory — Threat-focused advisory with MITRE mapping
  • ISO 42001 AIMS Readiness — AI governance compliance
  • Threat Assessment & Defense Guide — General threat modeling
  • Web Vulnerability Assessment — Web app security scanning
  • IT Risk Assessment Tool — IT risk scoring

Tips

  • OpenClaw users: scan your own agent to find and fix vulnerabilities
  • Agents with MCP servers and shell access have the highest risk profile
  • Enable human-in-the-loop for any agent with file system or code execution access
  • Use sandboxing to contain the blast radius of potential exploits
  • Scan after adding new skills or tools — each new capability expands attack surface
  • Combine with AgentSecly for both vulnerability scanning and threat advisory

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

91.49%
按下载量换算3,711

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills