Skip to main content
Glama

cortex_list_responders

List all enabled Cortex responders, optionally filtered by data type, to identify available automated response actions for security investigations.

Instructions

List all enabled responders, optionally filtered by data type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataTypeNoFilter by supported data type

Implementation Reference

  • The actual handler for the 'cortex_list_responders' tool. It calls client.listResponders(), optionally filters by dataType, maps responder fields to a summary, and returns JSON. On error, returns an isError response.
    server.tool(
      "cortex_list_responders",
      "List all enabled responders, optionally filtered by data type",
      {
        dataType: z
          .string()
          .optional()
          .describe("Filter by supported data type"),
      },
      async ({ dataType }) => {
        try {
          let responders = await client.listResponders();
    
          if (dataType) {
            responders = responders.filter((r) =>
              r.dataTypeList.includes(dataType),
            );
          }
    
          const summary = responders.map((r) => ({
            id: r.id,
            name: r.name,
            version: r.version,
            description: r.description,
            dataTypes: r.dataTypeList,
          }));
    
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(summary, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error listing responders: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • Input schema for cortex_list_responders: an optional 'dataType' string to filter by supported data type.
    {
      dataType: z
        .string()
        .optional()
        .describe("Filter by supported data type"),
    },
  • The 'cortex_list_responders' tool is registered via server.tool() inside the registerResponderTools() function in src/tools/responders.ts.
    export function registerResponderTools(
      server: McpServer,
      client: CortexClient,
    ): void {
      server.tool(
        "cortex_list_responders",
        "List all enabled responders, optionally filtered by data type",
        {
          dataType: z
            .string()
            .optional()
            .describe("Filter by supported data type"),
        },
        async ({ dataType }) => {
          try {
            let responders = await client.listResponders();
    
            if (dataType) {
              responders = responders.filter((r) =>
                r.dataTypeList.includes(dataType),
              );
            }
    
            const summary = responders.map((r) => ({
              id: r.id,
              name: r.name,
              version: r.version,
              description: r.description,
              dataTypes: r.dataTypeList,
            }));
    
            return {
              content: [
                {
                  type: "text" as const,
                  text: JSON.stringify(summary, null, 2),
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: `Error listing responders: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        },
      );
    
      server.tool(
        "cortex_run_responder",
        "Execute a responder action against a TheHive entity (case, task, artifact, alert)",
        {
          responderId: z.string().describe("The responder ID to execute"),
          objectType: z
            .enum(["case", "case_task", "case_artifact", "alert"])
            .describe("The type of TheHive entity to act on"),
          objectId: z
            .string()
            .describe("The ID of the entity from TheHive"),
          parameters: z
            .record(z.string(), z.unknown())
            .optional()
            .describe("Optional responder-specific parameters"),
        },
        async ({ responderId, objectType, objectId, parameters }) => {
          try {
            const actionJob = await client.runResponder(responderId, {
              objectType,
              objectId,
              parameters,
            });
    
            return {
              content: [
                {
                  type: "text" as const,
                  text: JSON.stringify(
                    {
                      actionJobId: actionJob.id,
                      status: actionJob.status,
                      responderId: actionJob.responderId,
                      responderName: actionJob.responderName,
                      message: `Responder action submitted. Job ID: "${actionJob.id}"`,
                    },
                    null,
                    2,
                  ),
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: `Error running responder: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        },
      );
    }
  • src/index.ts:8-36 (registration)
    Import and call to registerResponderTools() in the main index.ts to wire up the tool on the MCP server.
    import { registerResponderTools } from "./tools/responders.js";
    import { registerResponderDefinitionTools } from "./tools/responder-definitions.js";
    import { registerBulkTools } from "./tools/bulk.js";
    import { registerStatusTools } from "./tools/status.js";
    import { registerOrganizationTools } from "./tools/organizations.js";
    import { registerUserTools } from "./tools/users.js";
    import { registerResources } from "./resources.js";
    import { registerPrompts } from "./prompts.js";
    
    async function main(): Promise<void> {
      const config = getConfig();
    
      if (!config.verifySsl) {
        process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
      }
    
      const server = new McpServer({
        name: "cortex-mcp",
        version: "1.2.0",
        description:
          "MCP server for Cortex - observable analysis and active response engine by StrangeBee/TheHive Project",
      });
    
      const client = new CortexClient(config);
    
      // Core analysis tools
      registerAnalyzerTools(server, client);
      registerJobTools(server, client);
      registerResponderTools(server, client);
  • The client helper method client.listResponders() that makes the HTTP GET request to /responder and returns a list of Responder objects.
    async listResponders(): Promise<Responder[]> {
      return this.request<Responder[]>("/responder");
    }
Behavior2/5

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

With no annotations, the description carries the burden but only states basic functionality; it does not disclose if the operation is read-only, requires authentication, or any side effects.

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 concise sentence with no wasted words, appropriately sized for the tool's simplicity.

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?

Despite the tool's simplicity, the description lacks details about return values or what constitutes an 'enabled responder,' leaving some gaps given the absence of an output schema.

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 coverage is 100% for the single optional parameter, and the description adds no extra meaning beyond the schema's own description, resulting in baseline score.

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?

The description clearly states the tool lists all enabled responders with optional filtering by data type, effectively distinguishing it from sibling tools like cortex_list_responder_definitions.

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?

No guidance is provided on when to use this tool versus alternatives; it does not mention differences from list_responder_definitions or other list tools.

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/solomonneas/cortex-mcp'

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