Skip to main content
Glama
SLF Guardian MCP

SLF Guardian MCP

by slfguardian

check_command

Evaluates shell commands and SQL statements before execution, flags destructive or irreversible actions, and returns a verdict with safer alternatives—nothing is run.

Instructions

Check a shell command or SQL statement before running it and say whether it can be undone. Flags recursive and system-path deletes, disk writes, history and credential wiping, firewall changes, force push and hard reset, docker volume and kubernetes deletes, terraform destroy, cloud bucket and resource deletion, DROP/TRUNCATE and DELETE or UPDATE with no WHERE clause. Returns a verdict plus reversible, safe_to_run, needs_human_approval and a safer alternative per finding. Nothing is executed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoDefaults to auto.
commandNoCommand or statement to check.
commandsNoCheck a sequence in one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does well: it discloses that nothing is executed, enumerates the hazard classes it detects (recursive deletes, force push, terraform destroy, DROP/TRUNCATE, DELETE/UPDATE without WHERE), and lists the verdict fields returned. It does not cover ambiguous-input behavior or any limits on command length/complexity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the reversibility question, followed by a hazard list and return fields. The detection list is long but each item adds discriminating value; a bulleted structure would read better than one dense sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming the returned fields (verdict, reversible, safe_to_run, needs_human_approval, safer alternative). Combined with the explicit non-execution guarantee and hazard coverage, an agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so the schema already documents kind, command, and commands; baseline 3 applies. The description only loosely maps 'shell command or SQL statement' to the kind enum and never mentions the batch 'commands' array, so it adds little parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: check a shell command or SQL statement before execution and report whether it can be undone. The resource type (command/statement) plus the reversibility question clearly separates it from domain, package, prompt, or code scanners among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the timing: run this BEFORE running the command, and notes that nothing is executed, which tells the agent this is a safe pre-flight step. It does not name an alternative tool or state when-not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.