Skip to main content
Glama

security_xss_scan

Scans URLs for reflected XSS vulnerabilities by injecting 26 payload types and detecting unescaped reflections in responses.

Instructions

XSS vulnerability scanner: injects 26 XSS payloads (script tags, event handlers, SVG, template injection, etc.) into the target URL and detects unescaped payload reflection in the response body.

中文详情:

  • 用途:XSS 漏洞扫描,向目标 URL 注入 26 种 XSS payload(script 标签、事件处理器、SVG、模板注入等),检测响应体中是否未转义地包含 payload

  • 何时使用:搜索/评论/反馈等输入点上线前扫描时;URL 参数反射型 XSS 验证时;模板引擎转义回归时;OWASP A03 注入类风险验证时

  • 输出:{ ok: boolean, url: string, totalPayloads: number, vulnerable: boolean, findings: array } — 每项含 { payload, reflected: boolean, context: string, evidence }

  • 参数:

  • 错误:URL 无查询参数抛出 'No injectable parameters found';URL 不可达抛出 'Request failed'

  • 示例:{"url":"https://example.com/search?q=test"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes目标 URL,可包含查询参数如 http://example.com/page?q=test(必填)
Behavior4/5

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

With no annotations, description fully describes behavior: injects 26 payloads, checks reflection, includes errors and output structure. Could explicitly state non-destructive nature, but overall transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Bilingual structure adds redundancy (English summary repeated in Chinese). Well-organized with sections (purpose, when-to-use, output, params, errors), but could be more concise by removing duplicate content.

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?

Comprehensive: covers payload count, detection method, full output shape, parameter details, error cases, and example. Sufficient for an agent to use correctly without needing other references.

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?

Single parameter 'url' is documented in both schema and description. Description adds example and required flag, plus Chinese details. Schema coverage is 100%, so description adds marginal but useful context.

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?

Description clearly states 'XSS vulnerability scanner' and specifies it injects 26 payload types into target URLs, detecting unescaped reflection. Among sibling tools like security_sql_injection_scan and security_csp_analyze, this one is uniquely identified for XSS scanning.

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?

Chinese section explicitly lists when to use: pre-launch input scanning, reflected XSS validation, template regression, OWASP A03 verification. Does not explicitly state when not to use, but context from siblings (e.g., security_sql_injection_scan) implies it's for XSS only. Good guidance without exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server