Skip to main content
Glama

get_payloads

Lists available payloads for a specific Metasploit exploit to support authorized security testing and penetration testing workflows.

Instructions

List available payloads for a specific exploit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exploitPathYesFull exploit path

Implementation Reference

  • The handler function for the 'get_payloads' tool. It takes an exploitPath argument, uses the specified exploit in msfconsole, shows available payloads, and returns the results as JSON.
    case "get_payloads": {
      const { exploitPath } = args as { exploitPath: string };
    
      try {
        const payloads = await executeMsfCommand([
          `use ${exploitPath}`,
          `show payloads`,
        ]);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  success: true,
                  exploitPath,
                  payloads,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
        };
      }
    }
  • The tool definition including name, description, and input schema (JSON Schema) for 'get_payloads'.
    {
      name: "get_payloads",
      description: "List available payloads for a specific exploit",
      inputSchema: {
        type: "object",
        properties: {
          exploitPath: {
            type: "string",
            description: "Full exploit path",
          },
        },
        required: ["exploitPath"],
      },
    },
  • src/index.ts:219-220 (registration)
    Registration of the tools list handler which exposes the 'get_payloads' tool via the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
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 the tool lists payloads but doesn't describe what 'list' entails (e.g., format, pagination, or any side effects like authentication needs or rate limits). This leaves significant gaps in understanding how the tool behaves.

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 is appropriately sized and front-loaded, making it easy to grasp quickly.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns a list of payloads. It doesn't explain what the output looks like, any potential errors, or behavioral traits, leaving the agent with insufficient context to use the tool effectively.

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 schema description coverage is 100%, so the input schema already documents the 'exploitPath' parameter fully. The description adds no additional meaning beyond what's in the schema, such as examples or constraints, resulting in a baseline score of 3 where 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 tool's purpose with a specific verb ('List') and resource ('payloads for a specific exploit'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'search_exploits' or 'get_exploit_info', which might handle related but different functionality.

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 'get_exploit_info', nor does it mention any prerequisites or exclusions. It implies usage for listing payloads but lacks context about when this is appropriate.

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