Skip to main content
Glama

get_exploit_info

Retrieve detailed technical specifications and usage parameters for Metasploit Framework exploits to support authorized security testing and penetration testing workflows.

Instructions

Get detailed information about a specific exploit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exploitPathYesFull exploit path (e.g., 'exploit/windows/smb/ms17_010_eternalblue')

Implementation Reference

  • Handler for get_exploit_info tool: extracts exploitPath argument, executes 'info ${exploitPath}' command in msfconsole using executeMsfCommand helper, returns JSON with success/info or error.
    case "get_exploit_info": {
      const { exploitPath } = args as { exploitPath: string };
    
      try {
        const info = await executeMsfCommand([`info ${exploitPath}`]);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  success: true,
                  exploitPath,
                  info,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
        };
      }
    }
  • src/index.ts:109-123 (registration)
    Tool registration in the tools array, including name, description, and inputSchema defining required 'exploitPath' string.
    {
      name: "get_exploit_info",
      description: "Get detailed information about a specific exploit",
      inputSchema: {
        type: "object",
        properties: {
          exploitPath: {
            type: "string",
            description: "Full exploit path (e.g., 'exploit/windows/smb/ms17_010_eternalblue')",
          },
        },
        required: ["exploitPath"],
      },
    },
    {
  • Input schema for get_exploit_info: requires 'exploitPath' as string.
    inputSchema: {
      type: "object",
      properties: {
        exploitPath: {
          type: "string",
          description: "Full exploit path (e.g., 'exploit/windows/smb/ms17_010_eternalblue')",
        },
      },
      required: ["exploitPath"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets detailed information,' implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, or what the output format might be. This leaves significant gaps for a tool that likely interacts with exploit data.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the complexity of exploit information retrieval, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, output structure, or dependencies, leaving the agent with insufficient context for effective use.

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?

The input schema has 100% description coverage, with the 'exploitPath' parameter well-documented. The description adds no additional meaning beyond the schema, such as explaining the format further or providing examples beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('Get') and resource ('detailed information about a specific exploit'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'search_exploits' or 'search_auxiliary', which might have overlapping functionality, preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'search_exploits' or 'db_workspaces'. It lacks context about prerequisites, such as needing an exploit path, and doesn't mention any exclusions or specific scenarios for its use.

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/andreransom58-coder/kali-metasploit-mcp'

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