vulnerability_assessment · MCP Kali Pentest MCP

WHAT IT DOES

What vulnerability_assessment does on MCP Kali Pentest

AI agents invoke vulnerability_assessment to trigger actions in MCP Kali Pentest. 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 vulnerability_assessment needs a policy

This tool orchestrates multiple security tools (including exploitation frameworks like commix, crackmapexec, burpsuite_scan, etc.) in an automated manner. Running vulnerability assessments involves active probing, exploitation attempts, and code execution against targets.

From the tool's definition 'Comprehensive vulnerability assessment using multiple tools' on a server described as 'AI-powered autonomous penetration testing framework with 80+ professional security tools' including exploitation tools

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vulnerability_assessment Rate-limited

vulnerability_assessment 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": {
    "vulnerability_assessment": {
      "limits": [
        {
          "counter": "vulnerability_assessment_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 MCP Kali Pentest, so you can run agents against it safely.

FAQ

Questions about vulnerability_assessment

What does the vulnerability_assessment tool do? +

Comprehensive vulnerability assessment using multiple tools and AI analysis. It is categorised as a Execute tool in the MCP Kali Pentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vulnerability_assessment? +

Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for vulnerability_assessment: 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 MCP Kali Pentest. Nothing to install.

What risk level is vulnerability_assessment? +

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

Can I rate-limit vulnerability_assessment? +

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

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

vulnerability_assessment is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

vulnerability_assessment is one line of MCP Kali Pentest's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →