Skip to main content
Glama
tachote
by tachote

List sessions

list_interactsh_sessions

View cached interactsh sessions for security testing workflows. Enables monitoring of DNS/HTTP interactions captured during out-of-band testing with the MCP Interactsh Bridge server.

Instructions

Lists interactsh sessions cached in memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.js:333-340 (registration)
    Registers the 'list_interactsh_sessions' MCP tool with a simple handler that invokes service.listSessions() and wraps the result.
    server.registerTool(
      'list_interactsh_sessions',
      {
        title: 'List sessions',
        description: 'Lists interactsh sessions cached in memory.',
      },
      async () => result(service.listSessions()),
    );
  • The core handler logic within InteractshService that lists all cached sessions by iterating over the sessions Map and converting each to JSON.
    listSessions() {
      const result = {};
      for (const [key, session] of this.sessions.entries()) {
        result[key] = session.toJSON();
      }
      return result;
  • Helper function used by the tool handler to format the output with both text and structured content.
    function result(structured) {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(structured, null, 2),
          },
        ],
        structuredContent: structured,
      };
    }
  • InteractshSession class providing toJSON() method used by listSessions() to serialize session data.
    export class InteractshSession {
      constructor({ correlationId, secretKey, privateKey, publicKeyB64, callbackDomain, serverUrl }) {
        this.correlationId = correlationId;
        this.secretKey = secretKey;
        this.privateKey = privateKey;
        this.publicKeyB64 = publicKeyB64;
        this.callbackDomain = callbackDomain;
        this.serverUrl = serverUrl;
      }
    
      toJSON() {
        return {
          correlation_id: this.correlationId,
          secret_key: this.secretKey,
          private_key_pem: this.privateKey.export({ type: 'pkcs8', format: 'pem' }),
          callback_domain: this.callbackDomain,
          server_url: this.serverUrl,
        };
      }
    }
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 burden. It mentions that sessions are 'cached in memory', which adds some context about data persistence, but fails to disclose key behavioral traits like whether this is a read-only operation, potential rate limits, or the format of the returned list. The description is too minimal for a tool with no 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.

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 function without any wasted words. It is front-loaded and appropriately sized for a simple listing tool.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks details on output format or behavioral context, which could be important for an agent to use it correctly. It meets the basic requirement but has clear gaps in completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it implies the tool operates on cached data without requiring inputs, aligning well with the schema. A baseline of 4 is set for zero-parameter tools.

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 ('Lists') and resource ('interactsh sessions cached in memory'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'poll_interactsh_session', which might also involve listing or retrieving session data, so it doesn't fully achieve sibling differentiation.

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 'poll_interactsh_session' or 'create_interactsh_session'. It lacks context about prerequisites, such as whether sessions need to be created first, or exclusions for when not to use it.

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/tachote/mcp-interactsh'

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