scan_urls_batch · SQL Injection MCP Server MCP

WHAT IT DOES

What scan_urls_batch does on SQL Injection MCP Server

AI agents invoke scan_urls_batch to trigger actions in SQL Injection MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why scan_urls_batch needs a policy

Based on the server context and sibling tools (scan_url, scan_get_parameter, scan_post_parameter, continue_batch), this tool almost certainly performs bulk SQL injection scanning against multiple URLs. This constitutes active exploitation/probing of external systems — injecting payloads into web applications — which is an Execute-level action.

From the tool's definition Tool name 'scan_urls_batch' on a server described as 'An MCP server for identifying SQL injection vulnerabilities in web applications using various techniques like error-based, time-based, and union-based scanning.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_urls_batch Rate-limited

scan_urls_batch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_urls_batch": {
      "limits": [
        {
          "counter": "scan_urls_batch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SQL Injection MCP Server, so you can run agents against it safely.

FAQ

Questions about scan_urls_batch

What does the scan_urls_batch tool do? +

scan_urls_batch. It is categorised as a Execute tool in the SQL Injection MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_urls_batch? +

Register the SQL Injection MCP Server MCP server in PolicyLayer and add a rule for scan_urls_batch: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SQL Injection MCP Server. Nothing to install.

What risk level is scan_urls_batch? +

scan_urls_batch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scan_urls_batch? +

Yes. Add a rate_limit block to the scan_urls_batch rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block scan_urls_batch completely? +

Set action: deny in the PolicyLayer policy for scan_urls_batch. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides scan_urls_batch? +

scan_urls_batch is provided by the SQL Injection MCP Server MCP server (vivashu27/sqlinjector_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.