Execute Nikto web server scanner.
AI agents invoke nikto_scan to trigger actions in MCP Kali 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.
Nikto is an active web server scanner that probes target systems for vulnerabilities, misconfigurations, and dangerous files. It performs external operations against potentially unauthorized targets. The server context (Kali Linux, penetration testing) amplifies the risk.
From the tool's definition Execute Nikto web server scanner — runs an active web vulnerability scanning tool against target servers
Attacks that exploit this kind of access
Execute Nikto web server scanner. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Server MCP server in PolicyLayer and add a rule for nikto_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 MCP Kali Server. Nothing to install.
nikto_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 nikto_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 nikto_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.
nikto_scan is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.