AI agents invoke netdiscover_scan to trigger actions in Kali. 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.
netdiscover is a network address discovery tool that actively sends ARP packets to discover hosts on a network. On a Kali Linux pentesting server alongside tools like beef_exploit and autorecon_scan, this tool executes active network reconnaissance. The description is empty, reducing confidence slightly, but the tool name and server context strongly imply active network scanning execution.
From the tool's definition Tool name 'netdiscover_scan' on a Kali Linux MCP server described as providing 'network scanning, web scanning, password attacks' and related penetration testing tools. Sibling tools include active scanners and exploit frameworks.
Attacks that exploit this kind of access
netdiscover_scan. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for netdiscover_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. Nothing to install.
netdiscover_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 netdiscover_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 netdiscover_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.
netdiscover_scan is provided by the Kali MCP server (pentestt00ls/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →