Skip to main content
Glama
cfdude

Mac Shell MCP Server

get_whitelist

Retrieve the list of approved macOS terminal commands that can be securely executed through the Mac Shell MCP Server's whitelisting system.

Instructions

Get the list of whitelisted commands

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_whitelist' MCP tool call. It retrieves the whitelist from the CommandService and returns it as a JSON-formatted text content block.
    private async handleGetWhitelist() {
      const whitelist = this.commandService.getWhitelist();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(whitelist, null, 2),
          },
        ],
      };
    }
  • src/index.ts:111-118 (registration)
    Registration of the 'get_whitelist' tool in the MCP server's listTools response, including name, description, and empty input schema.
    {
      name: 'get_whitelist',
      description: 'Get the list of whitelisted commands',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Type definition for CommandWhitelistEntry, which represents the structure of whitelist entries 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;
    }
  • The getWhitelist method in CommandService that returns the array of all whitelisted commands from the internal Map.
    public getWhitelist(): CommandWhitelistEntry[] {
      return Array.from(this.whitelist.values());
    }
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 of behavioral disclosure. It states 'Get the list' which implies a read-only operation, but doesn't specify whether this requires authentication, returns paginated results, includes metadata, or has rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, clear sentence with no wasted words. It's front-loaded with the core purpose ('Get the list of whitelisted commands') and doesn't include unnecessary elaboration. Every word earns its place.

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 has no parameters and no output schema, the description is minimally adequate but lacks context about the return format (e.g., structure of the whitelist, data types) and behavioral traits. It meets the basic requirement for a simple read operation but doesn't provide enough information for confident use without additional context.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it appropriately doesn't mention any. Baseline 4 is correct for zero-parameter tools where the schema already covers everything.

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 action ('Get') and the resource ('list of whitelisted commands'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_pending_commands' or 'add_to_whitelist', but the verb+resource combination is specific enough to infer basic distinction.

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. It doesn't mention prerequisites, timing, or contrast with sibling tools like 'get_pending_commands' (which might retrieve unapproved commands) or 'add_to_whitelist' (which modifies the list). Usage is implied by the name but not explicitly stated.

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

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