Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Scan files for secrets with gitleaks rules

appsec-config_secrets-scan
Read-onlyIdempotent

Find secrets in text or diffs using vendored gitleaks rules with redaction. Price $0.04 USDC. POST /api/v1/appsec-config/secrets-scan. An unpaid call returns the x402 payment terms and does not run.

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": {
      "files": "<files>"
    },
    "name": "appsec-config_secrets-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomode, string, one of text, diff. Required.text
filesYesfiles, array. Required.
allowlistPathsNoallowlistPaths, array. Required.
includeLowEntropyNoincludeLowEntropy, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
suppressedNosuppressed. Array.
limitationsNolimitations. Array.
rulesVersionNorulesVersion. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: findings are redacted, the call costs $0.04 USDC, and an unpaid call short-circuits to x402 payment terms without performing the scan. That payment-gating disclosure is exactly the kind of operational context annotations cannot express.

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?

Four short sentences, front-loaded with the core purpose before pricing and endpoint details. The raw 'POST /api/v1/appsec-config/secrets-scan' path is arguably dead weight for an agent, but the payment and unpaid-call sentences carry real decision value.

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

Completeness4/5

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

With an output schema present, the description needn't explain return values, and annotations cover the safety profile. Combined with a brief note on redaction and the x402 payment prerequisite, an agent has enough to call this correctly; only explicit sibling routing is missing.

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 every parameter and nested field is already documented, giving a baseline of 3. The description only loosely maps to the parameters by mentioning 'text or diffs' (the mode enum); it says nothing about allowlistPaths or includeLowEntropy beyond what the schema states, so it adds little over the structured data.

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?

States a specific verb and resource ('Find secrets') plus the scope ('in text or diffs') and the rule set ('vendored gitleaks rules with redaction'). It never names a sibling or explicitly contrasts itself with the other appsec-config tools, but the resource is specific enough that confusion with nginx-config-audit or sbom-generate is unlikely.

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?

Usage is only implied by the purpose line – an agent can infer this is the tool for scanning supplied file content or diff patches for credentials. There is no explicit when-to-use/when-not statement, but the payment note does establish a practical precondition (the call must be paid before it will execute).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources