Skip to main content
Glama
cfdude

Mac Shell MCP Server

deny_command

Reject pending macOS terminal commands with a reason to maintain security controls in the Mac Shell MCP Server.

Instructions

Deny a pending command

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandIdYesID of the command to deny
reasonNoReason for denial

Implementation Reference

  • The main execution handler for the 'deny_command' tool. Validates input with Zod schema, calls CommandService.denyCommand, and returns a success or error response.
    private async handleDenyCommand(args: unknown) {
      const schema = z.object({
        commandId: z.string(),
        reason: z.string().optional(),
      });
    
      const { commandId, reason } = schema.parse(args);
    
      try {
        this.commandService.denyCommand(commandId, reason);
    
        return {
          content: [
            {
              type: 'text',
              text: `Command denied${reason ? `: ${reason}` : ''}`,
            },
          ],
        };
      } catch (error) {
        if (error instanceof Error) {
          return {
            content: [
              {
                type: 'text',
                text: `Command denial failed: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    }
  • The input schema definition for the 'deny_command' tool, registered in the ListTools response.
    {
      name: 'deny_command',
      description: 'Deny a pending command',
      inputSchema: {
        type: 'object',
        properties: {
          commandId: {
            type: 'string',
            description: 'ID of the command to deny',
          },
          reason: {
            type: 'string',
            description: 'Reason for denial',
          },
        },
        required: ['commandId'],
      },
  • src/index.ts:238-239 (registration)
    The dispatch/registration of the 'deny_command' handler in the CallToolRequestSchema switch statement.
    case 'deny_command':
      return await this.handleDenyCommand(args);
  • The supporting denyCommand method in CommandService that handles the actual denial logic: removes from pending, emits event, and rejects the promise.
      public denyCommand(commandId: string, reason: string = 'Command denied'): void {
        const pendingCommand = this.pendingCommands.get(commandId);
        if (!pendingCommand) {
          throw new Error(`No pending command with ID: ${commandId}`);
        }
    
        // Remove from pending queue
        this.pendingCommands.delete(commandId);
    
        // Emit event for denied command
        this.emit('command:denied', { commandId, reason });
    
        // Reject the original promise
        pendingCommand.reject(new Error(reason));
      }
    }
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. It states the action ('deny') but doesn't explain what 'deny' entails—whether it's reversible, if it requires specific permissions, what the outcome is, or if there are side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 with zero wasted words. It's front-loaded with the core action and target, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain the tool's behavior, outcomes, or error conditions. The agent lacks context on what 'deny' means operationally, making it difficult to use correctly without additional information.

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?

The input schema has 100% description coverage, with clear documentation for both parameters ('commandId' and 'reason'). The description doesn't add any meaning beyond what the schema provides, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the schema handles parameter semantics adequately.

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 ('deny') and the target ('a pending command'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'approve_command' or explain what 'deny' means in this context beyond the basic action.

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 'approve_command' or 'execute_command'. It doesn't mention prerequisites (e.g., needing a pending command ID) or context about what happens after denial. 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/cfdude/mac-shell-mcp'

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