Skip to main content
Glama

fsv_scan

Run authorized web vulnerability scans against a target URL, crawl site pages, and return severity-ranked security findings with remediation guidance.

Instructions

Run a web vulnerability scan against a target URL. Crawls the site (same-origin, skips logout/asset links) and runs modules by profile: 'passive' sends no payloads (headers, SSL/TLS, DNS, cookies, WAF, fingerprint, JWT, CSP, SRI, security.txt); 'balanced' (default) adds safe active checks (XSS, SQLi, CORS, open-redirect, SSTI, host-header); 'aggressive' is the same modules at higher rate/concurrency; 'deep' is thorough (wider crawl, hidden-parameter discovery, larger exposed-file list, more payload shapes — many more requests, only for targets the user owns); 'full' is exhaustive (1000+ URLs at depth 6, ~600 guessed directories/pages, backup copies of every script, boolean SQLi, 160 parameter names — the slowest and busiest; always set max_minutes). Returns findings grouped with severity, CWE, OWASP category, confidence and remediation. Time-boxed by max_minutes (default 20; partial results are kept). use_ct_logs=true also asks Certificate Transparency logs (crt.sh) for subdomains (sends the domain to a third party — only with the user's consent); allow_external=false skips modules that contact hosts other than the target. seed_urls adds same-origin pages no link points to; headers/cookies make it an authenticated scan (use a test account, never a real user's session). Only scan targets the user owns or is authorized to test; pass authorized=true only after they confirm.

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>",
      "authorized": "<authorized>"
    },
    "name": "fsv_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawlNo
depthNo
targetYes
cookiesNo
headersNo
modulesNo
profileNobalanced
max_urlsNo
seed_urlsNo
authorizedYes
max_minutesNo
use_ct_logsNo
exclude_pathsNo
allow_externalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With zero annotations, the description carries the full behavioral burden. It details critical constraints: the crawl skips logout/asset links, CT logs involve sending data to a third party, and the tool is time-boxed returning partial results if `max_minutes` is reached.

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?

While the definition is long, its length is completely justified by the extreme complexity of the tool and the lack of structured data. It is highly efficient, grouping similar concepts (like profiles) logically.

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

Completeness5/5

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

Given that the tool is highly complex, involves ethical constraints, and has zero structured guidance (annotations/schema descriptions), this definition is maximally complete. An agent would have nearly all the necessary context to deploy it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema description coverage is 0%, the description must compensate. It does so perfectly by explaining the purpose and scope of almost every complex parameter, such as detailing what each 'profile' entails or why `seed_urls` is useful.

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 immediately states the tool's function: 'Run a web vulnerability scan against a target URL.' This is precise, and the list of sibling tools confirms this is the primary scanning action.

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

Usage Guidelines5/5

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

The description offers exhaustive guidelines, defining specific operational modes like 'passive', 'balanced', and 'full'. Crucially, it also provides ethical/legal boundaries ('Only scan targets the user owns or is authorized to test') which are vital for usage.

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