Skip to main content
Glama

guard_inspect

Audit commands or code snippets before execution to detect secret leaks, SQL injection, TLS bypass, CORS wildcards, destructive commands, raw grep, and never-terminating streams.

Instructions

Pre-flight security & hygiene audit for commands or code snippets. Detects secret leaks, SQL injection, TLS bypass (incl. git-level), CORS wildcard, destructive commands, raw grep, and never-terminating streams (tail -f, watch, docker attach).

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": "guard_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional: Code snippet, replacement diff, or file content to audit
commandNoOptional: Terminal command line to audit
file_pathNoOptional: File path being written or modified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.4

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does useful work by listing the concrete detection categories (secret leaks, SQL injection, TLS bypass, CORS wildcard, destructive commands, never-terminating streams), but it never says whether a hit blocks execution or merely reports, what severity model applies, or what the response contains.

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?

Two tight sentences with the purpose front-loaded and the detection list packed into a single scannable clause. No filler and no repetition of the tool name.

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?

The tool has no annotations and no output schema, so the description is the only source of behavioral information. It adequately covers what is checked but leaves the outcome contract, severity semantics, and required-input expectations undocumented — meaningful gaps for an audit/gate tool.

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% and all three parameters are self-documented and optional, so the baseline is 3. The description adds little beyond the schema: it maps loosely to 'commands or code snippets' but does not explain the role of file_path or whether at least one input is required.

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 gives a specific verb and resource ('Pre-flight security & hygiene audit for commands or code snippets') and enumerates the exact classes of problems detected, so an agent knows precisely what it screens for. It stops short of distinguishing itself from related siblings such as sanitize_command, leaving the agent to infer the boundary from names alone.

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?

'Pre-flight' is a clear timing cue: invoke it before executing a command or writing code. There are no explicit exclusions or named alternatives, so the when-not-to-use side is left implicit.

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