Perform automated vulnerability assessment with multiple tools
AI agents invoke vulnerability_scan to trigger actions in Kali 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.
This tool executes active security scanning and vulnerability assessment against targets using multiple penetration testing tools. It triggers external network operations and runs security probes against systems, which can have significant side effects including triggering IDS/IPS alerts, disrupting services, or exposing sensitive system information.
From the tool's definition 'Perform automated vulnerability assessment with multiple tools' on a Kali Linux server with 'automated vulnerability scanning' and 'penetration testing tools'
Documented attack patterns abuse exactly the kind of access vulnerability_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for vulnerability_scan:
{
"version": "1",
"default": "deny",
"tools": {
"vulnerability_scan": {
"limits": [
{
"counter": "vulnerability_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}vulnerability_scan 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.
Free to start. No card required.
Perform automated vulnerability assessment with multiple tools. It is categorised as a Execute tool in the Kali MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP Server MCP server in PolicyLayer and add a rule for vulnerability_scan: 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 Kali MCP Server. Nothing to install.
vulnerability_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vulnerability_scan 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.
Set action: deny in the PolicyLayer policy for vulnerability_scan. 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.
vulnerability_scan is provided by the Kali MCP Server MCP server (k3nn3dy-ai/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Kali MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.