Skip to main content
Glama
Sign In
mcp-security-scanner

mcp-security-scanner

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sast_path_traversal

Scans code for path traversal vulnerabilities: detects unsafe use of fs functions (readFile, writeFile, readdir, unlink) with user input missing path.resolve validation.

Instructions

AST-scan for path traversal: fs.readFile(), writeFile(), readdir(), unlink() — where path argument includes user input without path.resolve() validation.

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": {
      "path": "<path>"
    },
    "name": "sast_path_traversal"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDirectory path containing source files to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden. It states the tool performs an AST-scan (static analysis, non-destructive), but it does not disclose details such as output format, performance characteristics, or whether results include line numbers or file paths. The description is minimal.

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?

The description is a single sentence that is front-loaded with the tool's purpose ('AST-scan for path traversal') and lists key functions. Every word is informative, with no redundancy.

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?

For a simple tool with one parameter and no output schema, the description adequately covers what the tool does. However, it could benefit from mentioning the output format (e.g., list of vulnerable paths) or any limitations (e.g., only checks specific functions). Minor gaps prevent a 5.

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 coverage is 100% (the only parameter 'path' is described as 'Directory path containing source files to analyze'). The description adds no additional meaning about parameter format, allowed values, or behavior beyond what the schema provides. Baseline 3 is appropriate.

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?

The description explicitly states it is an AST-scan for path traversal vulnerabilities, listing specific functions (fs.readFile(), writeFile(), readdir(), unlink()) and the condition (user input without path.resolve() validation). This clearly differentiates it from sibling tools like sast_code_execution or sast_command_injection.

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?

The description implies use for detecting path traversal issues but does not explicitly state when to use this tool versus alternatives. It provides no exclusion criteria or hints about complementary tools.

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