continue_batch · SQL Injection MCP Server MCP: Risk & Policy

WHAT IT DOES

What continue_batch does on SQL Injection MCP Server

AI agents invoke continue_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 continue_batch needs a policy

This tool resumes execution of SQL injection scanning operations against external web applications. It actively sends crafted payloads to target URLs, which constitutes triggering external operations with effects depending on arguments.

From the tool's definition 'Continue scanning remaining URLs from a previous batch' — resumes active security scanning operations (error-based, time-based, union-based SQL injection probing) against web application endpoints

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

continue_batch Rate-limited

continue_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": {
    "continue_batch": {
      "limits": [
        {
          "counter": "continue_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 continue_batch

What does the continue_batch tool do? +

Continue scanning remaining URLs from a previous 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 continue_batch? +

Register the SQL Injection MCP Server MCP server in PolicyLayer and add a rule for continue_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 continue_batch? +

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

Can I rate-limit continue_batch? +

Yes. Add a rate_limit block to the continue_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 continue_batch completely? +

Set action: deny in the PolicyLayer policy for continue_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 continue_batch? +

continue_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.