Skip to main content
Glama
StrawHatAI

Claude Desktop Commander MCP

by StrawHatAI

list_blocked_commands

View currently blocked terminal commands to understand security restrictions and manage command execution permissions in the Claude Desktop Commander environment.

Instructions

List all currently blocked commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:114-123 (registration)
    Tool registration in the ListTools response, including name, description, and empty input schema.
    {
      name: "list_blocked_commands",
      description:
        "List all currently blocked commands.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • MCP tool dispatch handler that calls commandManager.listBlockedCommands() and formats the response.
    case "list_blocked_commands": {
      const blockedCommands = await commandManager.listBlockedCommands();
      return {
        content: [{ type: "text", text: blockedCommands.join('\n') }],
      };
    }
  • Core implementation of listing blocked commands from the internal Set, sorted alphabetically.
    listBlockedCommands(): string[] {
      return Array.from(this.blockedCommands).sort();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, it doesn't specify whether this requires special permissions, how results are formatted, if there are rate limits, or what 'currently' means in terms of freshness. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place in this minimal description.

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?

For a simple list tool with no parameters and no output schema, the description provides the basic purpose but lacks important context. Without annotations or output schema, the description should ideally mention what format the blocked commands are returned in or any limitations. It's minimally adequate but leaves the agent guessing about the response structure.

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 with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. The baseline for zero parameters with full schema coverage is 4, as there's no parameter information needed beyond what's already structured.

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 ('List') and resource ('blocked commands'), making the purpose immediately understandable. It specifies 'all currently blocked commands' which adds useful scope information. However, it doesn't explicitly differentiate from sibling tools like 'unblock_command' or 'block_command'.

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. There's no mention of when this tool is appropriate versus 'list_allowed_directories' or 'list_sessions', nor any prerequisites or context for usage. The agent must infer usage 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/StrawHatAI/claude-dev-tools'

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