Skip to main content
Glama
mcp-security-auditor

mcp-security-auditor

by jashory

remediate_path

Redacts hardcoded secrets or restores a clean static redirect index.html in a local directory or file before git push, helping prevent credential leaks or unwanted redirects.

Instructions

Automatically redact hardcoded secrets or restore clean static redirect index.html in a local directory or file before git push.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "remediate_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesLocal directory or file path to auto-remediate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the non-obvious dual behavior (secret redaction vs. restoring a clean index.html) and the git-push context, which is genuinely useful. However, it omits the traits that matter most for an in-place mutation: whether files are overwritten irreversibly, whether backups or diffs are produced, and what happens on partial failure.

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?

A single front-loaded sentence with no filler, and the operative verbs appear early. The compound 'or' clause and trailing 'before git push' qualifier make it slightly denser than ideal for one line, but nothing is wasted.

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?

With no annotations, no output schema, and one fully documented parameter, the description covers what the tool does but not the outcome contract: no mention of what is reported back, whether changes are logged, or how partial remediation is signaled. For a destructive file-mutating tool this leaves a real operational gap, though the small surface area keeps it from being severe.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already fully documents 'target'. The description adds the notion that the path can be either a directory or a file, matching the schema, but contributes no format, relative-path, or validation details beyond it. Baseline 3 applies.

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 names a specific verb pair (redact / restore) tied to concrete resources (hardcoded secrets, static redirect index.html) and a target (local directory or file). It implicitly contrasts with the sibling scan_path by promising action rather than inspection, though it never names an alternative. The dual-mode 'or' phrasing is slightly ambiguous about which remediation will fire given a given target.

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

Usage Guidelines3/5

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

It supplies a timing cue ('before git push'), which implies when in a workflow to invoke it. It does not state preconditions (must the path be inside a git repo?), what happens if nothing is found, or when to prefer scan_path first. Usage is implied rather than prescribed.

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

Deploy Server

Other Tools