Skip to main content
Glama
vivashu27

SQL Injection MCP Server

by vivashu27

scan_urls_batch

Batch scan URLs for SQL injection vulnerabilities with configurable injection types, database types, and quick mode to prevent timeouts. Supports concurrency and WAF bypass.

Instructions

Scan multiple URLs for SQL injection vulnerabilities in batch. Use quick_mode=True (default) for faster scans that won't timeout.

Args: urls: Newline-separated list of URLs to scan method: HTTP method - GET or POST injection_types: Comma-separated injection types (default: error_based only in quick_mode) database_types: Comma-separated database types (default: generic,mysql in quick_mode) headers: Custom headers as key:value pairs separated by | cookies: Cookies as key=value pairs separated by ; bearer_token: Bearer token for Authorization header proxy_url: Proxy URL for Burp Suite or other proxies verify_ssl: Verify SSL certificates waf_bypass: WAF bypass technique concurrency: Number of concurrent scans (1-10, default 3) timeout: Request timeout in seconds per URL (default 5) quick_mode: Use quick scan with fewer payloads (default True, recommended for many URLs) max_urls_per_batch: Max URLs to scan in one call (default 10, use continue_batch for more)

Returns: Batch scan results. If more URLs remain, use continue_batch with the batch_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYes
methodNoGET
injection_typesNo
database_typesNo
headersNo
cookiesNo
bearer_tokenNo
proxy_urlNo
verify_sslNo
waf_bypassNonone
concurrencyNo
timeoutNo
quick_modeNo
max_urls_per_batchNo
Behavior3/5

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

No annotations provided; description covers concurrency, timeout, and quick_mode defaults but does not disclose potential destructive impact (SQL injection probing), auth requirements, or error behavior.

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?

Well-structured with a clear opening and bulleted parameter list, though slightly longer than necessary (9 lines).

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?

Covers input comprehensively and mentions batching continuation, but lacks details on return format and error handling. Output schema is absent.

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?

With 0% schema coverage, the description thoroughly explains every parameter including format and defaults, far exceeding the baseline.

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?

Clearly states it scans multiple URLs for SQL injection vulnerabilities in batch, distinguishing it from single-URL tools like scan_url and from file-based scan_urls_from_file.

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?

Provides guidance on quick_mode for faster scans and mentions continue_batch for more URLs, but lacks explicit when-not-to-use compared to siblings like scan_url or test_payload.

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/vivashu27/SQLinjector_MCP'

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