Skip to main content
Glama

security_sql_injection_scan

Scans target URL query parameters for SQL injection vulnerabilities by injecting 20 payloads and detecting database error leaks in responses.

Instructions

SQL injection vulnerability scanner: injects 20 SQLi payloads into the target URL's query parameters and detects SQL error leakage (MySQL, Oracle, PostgreSQL, SQL Server, SQLite) in responses.

中文详情:

  • 用途:SQL 注入漏洞扫描,向目标 URL 的查询参数注入 20 种 SQL 注入 payload,检测响应中是否泄露 SQL 错误信息

  • 何时使用:上线前 SQL 注入漏洞扫描时;查询参数(如 ?id=1)可疑时;接口输入校验回归时;OWASP A03 注入类风险验证时

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

  • 参数:

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

  • 示例:{"url":"https://example.com/product?id=1"}

Input Schema

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

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

Without annotations, the description details the scanning process (20 payloads, DBMS detection), output format, and error handling. It does not mention authorization needs or potential side effects, but the behavior is well described.

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 concise and well-structured: an English summary followed by Chinese bullet points for key aspects (usage, output, parameters, errors, example). No unnecessary words.

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?

Given the single parameter and no output schema, the description is fairly complete. It covers purpose, when to use, parameter details, output shape, error cases, and an example. It could mention that it only scans query parameters (not POST bodies), but overall it's sufficient.

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?

The url parameter is described in both the schema and the description with examples and error conditions. The description adds context that query parameters are expected and provides a sample input, going beyond the schema's type and required flag.

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 clearly states it is a SQL injection vulnerability scanner that injects 20 SQLi payloads and detects error leakage. It distinguishes from sibling tools like security_xss_scan and security_headers_check by naming the specific vulnerability type and technique.

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 Chinese section explicitly lists when to use: pre-release scanning, suspicious query parameters, regression testing, OWASP A03 verification. It also mentions error cases (no injectable parameters, unreachable URL).

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