Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

metasploit_search

Search the Metasploit database by keyword or module type to find exploits, payloads, and auxiliary, post, encoder, or NOP modules for penetration testing.

Instructions

Search Metasploit database for exploits, payloads, or modules

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "metasploit_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoModule type: exploit, payload, auxiliary, post, encoder, nopall
queryYesSearch query (e.g., 'apache', 'windows smb', 'type:exploit platform:linux')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether this hits a local Metasploit instance or remote API, whether results are capped or paginated, or how failures appear. It only conveys the generic notion of a read-only lookup, which is not enough for a tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity contributes to the gaps in usage and behavioral detail noted elsewhere.

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?

For a two-parameter search tool the description is adequate to invoke correctly, and the schema documents both parameters fully. However, with no output schema, the description should hint at what a search returns (module names, ranks, descriptions) and any result limits, which it omits.

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

Parameters3/5

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

Schema description coverage is 100%: the 'type' parameter enumerates module types and 'query' includes example syntax such as 'type:exploit platform:linux'. The description adds no meaning beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

The description names a specific verb (search) and resource (Metasploit database) plus the object types searched (exploits, payloads, modules), which is enough to separate it from metasploit_exploit_info at a high level. It stops short of explicitly contrasting itself with that sibling, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (metasploit_exploit_info) for retrieving details on a specific module. Usage is only implied by the word 'search'.

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