Skip to main content
Glama

Search Exploits

search_exploits
Read-onlyIdempotent

Browse and filter exploits by source, attack type, reliability, CVE, vendor, or author to find weaponizable PoCs, Metasploit modules, and exploit code for security testing.

Instructions

Browse and filter exploits using STRUCTURED FILTERS ONLY (no free-text query). Use this to filter by source (github, metasploit, exploitdb, nomisec, gitlab, inthewild, vulncheck_xdb, patchapalooza, oscs, poc_monitor), language (python, ruby, etc.), LLM classification (working_poc, trojan, suspicious, scanner, stub, writeup, tool, no_code), author, min stars, code availability, CVE ID, vendor, or product. Also filter by AI analysis: attack_type (RCE, SQLi, XSS, DoS, LPE, auth_bypass, info_leak), complexity (trivial/simple/moderate/complex), reliability (reliable/unreliable/untested/theoretical), requires_auth. NOTE: To search by product name (e.g. 'OpenSSH', 'Apache'), use search_vulnerabilities instead — it has free-text query and get_vulnerability already includes exploits in the response. Examples: source='metasploit' for all Metasploit modules; attack_type='RCE' with reliability='reliable' for weaponizable RCE exploits; cve='CVE-2024-3400' for all exploits targeting a specific CVE; vendor='mitel' for all Mitel exploits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoFilter by source
languageNoFilter by language: python, ruby, go, c, etc.
llm_classificationNoFilter by LLM classification
attack_typeNoFilter by attack type from AI analysis (case-insensitive on input; canonical casing returned)
complexityNoFilter by exploit complexity
reliabilityNoFilter by exploit reliability
requires_authNoFilter by whether exploit requires authentication
authorNoFilter by author name
min_starsNoMinimum GitHub stars
has_codeNoOnly exploits with downloadable code
cveNoFilter by CVE ID (e.g. 'CVE-2024-3400') — returns all exploits for that CVE
vendorNoFilter by vendor name (e.g. 'mitel', 'fortinet') — returns exploits for all CVEs affecting that vendor
productNoFilter by product name (e.g. 'micollab', 'pan-os')
sortNoSort order
pageNoPage number (default: 1)
per_pageNoResults per page (1-25, default: 10)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this as a safe, read-only, idempotent operation. The description adds the constraint of structured filters only but does not disclose much beyond what annotations and schema cover, such as return format or pagination details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with the primary constraint first, then filter categories, a note about alternatives, and examples. Some redundancy remains (e.g., listing enum values both in description and schema), but overall efficient for the content load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers input semantics thoroughly given the complexity (16 parameters) and lack of output schema. However, it does not describe what the response contains (e.g., fields, pagination behavior), which would be helpful for a tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with individual descriptions, so baseline is 3. The description adds value by grouping filters into categories, giving composite usage examples (e.g., attack_type='RCE' with reliability='reliable'), and explaining the alternative for product search.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool browses and filters exploits using structured filters only. Distinguishes from sibling search_vulnerabilities by explicitly noting the lack of free-text query and directing product name searches to the alternative tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use and when not to use, including a direct reference to search_vulnerabilities for product name searches. Provides multiple concrete examples demonstrating filter combinations for typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exploitintel/eip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server