Vulnerability Scanning Tools for AI Agents logopeterindia.net
Knowledge Hub

Vulnerability Scanning Tools for AI Agents

Tools that test AI agents for weaknesses such as prompt injection, tool abuse and unsafe MCP servers, plus agentic tools that scan code for vulnerabilities.

51 topics•7 categories•Updated October 2026

Two Meanings of the Topic

3 entries

The phrase covers two different jobs. The first is scanning AI agents themselves: probing models and agents for prompt injection, data leakage, jailbreaks and unsafe tool use, and checking the MCP servers, skills and model files they depend on. The second is using AI agents as scanners that find, reproduce and patch vulnerabilities in other software. This page lists both. Agents differ from ordinary applications because they act on untrusted text, call tools with real credentials and change behaviour between runs, so a one-off scan is not enough; results should feed continuous testing.

LLM & Agent Red-Teaming Scanners

11 entries

Automated probing of models and agents for jailbreaks, injection and unsafe behaviour.

MCP Server & Agent Skill Scanners

7 entries

Check the tools and extensions an agent loads before it trusts them.

Model File & Supply Chain Scanners

7 entries

Detect malicious code and tampering in downloaded models and dependencies.

AI Agents That Find & Fix Code Vulnerabilities

10 entries

Agentic tools that scan source code, reproduce findings and propose patches. Verify their output manually.

Runtime Guardrails & Detection

6 entries

Block attacks that scanning could not prevent.

Related Pages

7 entries

Neighbouring pages on this site.

Frequently Asked Questions

What does vulnerability scanning for AI agents mean?

Testing agents for weaknesses such as prompt injection, data leakage and unsafe tool use, and checking the MCP servers, skills and model files they rely on. It can also mean using AI agents to scan other software for vulnerabilities.

How is it different from a normal vulnerability scan?

Conventional scanners match known flaws in code and packages. Agents add behavioural risks: they follow instructions hidden in content, act with real credentials and may respond differently each run, so tests must be repeated and combined with runtime controls.

Which tools should I start with?

Open-source options such as garak, PyRIT and Promptfoo cover model and agent red teaming, and MCP and skill scanners cover the tools an agent loads. Add dependency and container scanning for the code around the agent.

Can AI agents be trusted to find vulnerabilities?

They can speed up discovery, but they produce false positives and inaccurate patches. Google makes the same point about Mantis, so have a security engineer verify findings and run the tools in isolation from production.

How current is this page?

Links and project activity were checked in October 2026. This area changes quickly: projects are renamed, acquired or archived, and several tools are vendor products whose claims are the vendors' own. Sites that block automated checks are kept and may need a manual click. No scanner finds every flaw, so treat results as input to human review.