Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Scan a file for injection sinks

appsec-config_injection-sink-scan
Read-onlyIdempotent

Lightweight single-file taint scan for SQL, command and XSS sinks. Price $0.03 USDC. POST /api/v1/appsec-config/injection-sink-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": {
      "language": "<language>",
      "content": "<content>"
    },
    "name": "appsec-config_injection-sink-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNopath, string. Required.input
contentYescontent, string, length 0 to 500000. Required.
languageYeslanguage, string, one of javascript, typescript, python. Required.

Output Schema

NameRequiredDescriptionDefault
scopeNoscope. String.
caveatNocaveat. String.
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: a $0.03 USDC price, the POST endpoint, and that an unpaid call returns x402 payment terms without executing — critical for an agent to avoid a silent no-op.

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?

Three short sentences, front-loaded with the capability, then cost/endpoint, then the failure mode. Every sentence carries distinct information and nothing is padded.

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 need not explain results, and annotations cover the safety profile; parameters are fully documented in the schema. The remaining gap is only the absence of stated limits on sink coverage or scan depth, which is minor for a lightweight scan.

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 each parameter carries its own description plus a language enum, so the schema does the heavy lifting. The description adds nothing about path vs content semantics or how language affects detection; 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 and resource ('single-file taint scan') and scopes the finding types to 'SQL, command and XSS sinks'. That is concrete enough to separate it from siblings like appsec-config_secrets-scan or appsec-config_regex-redos-check, though it never explicitly contrasts itself with them.

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: 'lightweight single-file' tells an agent this is a per-file, non-exhaustive check, and the payment sentence explains the unpaid-call path. There is no explicit statement of when to prefer this over a sibling scan or what preconditions (language, file size) must hold.

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