Skip to main content
Glama
vutiendat284

Web Pentest MCP Server

by vutiendat284

browse_wstg_catalog

Search and filter the OWASP Web Security Testing Guide catalog by keyword or section to find relevant security test cases for web pentesting.

Instructions

Tra cứu Từ điển Kiểm thử An ninh Chuẩn OWASP Web Security Testing Guide (WSTG) v4.2. Gồm 13 chuyên đề và 119 bài kiểm tra bảo mật từ workbook pentest 2026.

📌 HƯỚNG DẪN THỰC HIỆN:

  1. Tìm kiếm theo từ khóa: Nhập từ khóa kỹ thuật vào ô 'query' (ví dụ: 'header', 'ssl', 'injection', 'cors', 'auth').

  2. Lọc theo chuyên đề: Chọn tên nhóm từ danh sách Dropdown 'section' (ví dụ: 'Information Gathering', 'Configuration and Deployment Management').

  3. Phân trang: Điều chỉnh 'offset' và 'limit' nếu danh sách kết quả lớn.

💡 VÍ DỤ MINH HỌA:

  • Ví dụ 1: Tìm tất cả các bài kiểm tra bảo mật liên quan đến HTTP Header: browse_wstg_catalog(query="header", limit=10)

  • Ví dụ 2: Liệt kê các bài test thuộc nhóm Thu thập thông tin (INFO): browse_wstg_catalog(section="Information Gathering", limit=20)

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
sectionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/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 burden. It implies a read-only lookup and discloses pagination via offset/limit and that results can be large, but it does not say how 'query' matches (substring? case-insensitive?), whether query and section combine with AND, or what the default limit of 150 means.

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?

Front-loaded with the resource description, then a numbered how-to and examples. The emoji-laden formatting and example block add some bulk, but each section serves a purpose and it is easy to scan.

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?

An output schema exists so return values needn't be described. For a 4-param, zero-annotation browse tool, the description covers all parameters and usage patterns; the remaining gaps are default values and filter-combination semantics.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it explains 'query' as technical keyword search with examples, 'section' as a dropdown group with example values, and 'offset'/'limit' as pagination. It omits the default values and the interaction semantics between query and section.

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+resource: tra cứu (look up) the OWASP WSTG v4.2 catalog, with scope quantified (13 sections, 119 tests). It implicitly separates itself from run_wstg_test by being a catalog lookup rather than test execution, but it never names a sibling explicitly.

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

Usage Guidelines4/5

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

Three numbered steps plus two worked examples give clear guidance on when to use keyword search vs section filtering vs pagination. It lacks explicit when-not-to-use guidance and does not name alternatives like run_wstg_test for actually executing a test.

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