scan_post_parameter · SQL Injection MCP Server MCP

WHAT IT DOES

What scan_post_parameter does on SQL Injection MCP Server

AI agents invoke scan_post_parameter 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_post_parameter needs a policy

Based on the server context, this tool likely scans POST parameters for SQL injection vulnerabilities by actively sending malicious payloads to target web applications. This constitutes execution of potentially destructive SQL injection attacks against external systems. The sibling tools (scan_url, scan_urls_batch, get_waf_bypass_payloads) confirm active attack/testing capabilities.

From the tool's definition Tool name 'scan_post_parameter' on a server described as performing SQL injection vulnerability scanning using 'error-based, time-based, and union-based scanning' with 'WAF bypass strategies'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_post_parameter Rate-limited

scan_post_parameter 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_post_parameter": {
      "limits": [
        {
          "counter": "scan_post_parameter_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_post_parameter

What does the scan_post_parameter tool do? +

scan_post_parameter. 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_post_parameter? +

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

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

Can I rate-limit scan_post_parameter? +

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

Set action: deny in the PolicyLayer policy for scan_post_parameter. 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_post_parameter? +

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