Skip to main content
Glama
cfdude

Super Shell MCP Server

get_whitelist

Retrieve the list of approved shell commands that can be executed securely across Windows, macOS, and Linux systems.

Instructions

Get the list of whitelisted commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_whitelist' that fetches the whitelist from CommandService and returns it as formatted JSON.
    private async handleGetWhitelist() {
      const whitelist = this.commandService.getWhitelist();
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(whitelist, null, 2),
          },
        ],
      };
    }
  • src/index.ts:170-177 (registration)
    Registration of the 'get_whitelist' tool in the ListToolsRequestSchema handler, defining its name, description, and empty input schema.
    {
      name: 'get_whitelist',
      description: 'Get the list of whitelisted commands',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Type definition for CommandWhitelistEntry, the structure of objects in the whitelist returned by get_whitelist.
    export interface CommandWhitelistEntry {
      /** The command path or name */
      command: string;
      /** Security level of the command */
      securityLevel: CommandSecurityLevel;
      /** Allowed arguments (string for exact match, RegExp for pattern match) */
      allowedArgs?: Array<string | RegExp>;
      /** Description of the command for documentation */
      description?: string;
    }
  • Core helper method in CommandService that converts the internal whitelist Map to an array for the tool handler.
    public getWhitelist(): CommandWhitelistEntry[] {
      return Array.from(this.whitelist.values());
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, or what format the returned list has. This is inadequate 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.

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 with no wasted words. It's perfectly front-loaded and appropriately sized for a simple retrieval tool.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns structured data. It doesn't explain what 'whitelisted commands' entails, the return format, or any behavioral context, leaving significant gaps for an agent to use it correctly.

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 tool has zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here, warranting a baseline score above minimum viable.

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 ('list of whitelisted commands'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_pending_commands' or 'get_platform_info' beyond the resource name, which prevents 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 'get_pending_commands' or 'add_to_whitelist'. There's no mention of prerequisites, context, or exclusions, leaving usage entirely implicit from the tool name alone.

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/cfdude/super-shell-mcp'

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