AI agents invoke tools_masscan to trigger actions in Zebbern Kali MCP. 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.
Masscan is a well-known network reconnaissance tool used to perform large-scale port scanning. Even though the description is empty, the tool name clearly references masscan, which executes network scans against external targets. In the context of a Kali Linux pentesting server with highly offensive sibling tools, this tool executes active network scanning operations.
From the tool's definition Tool name 'tools_masscan' on a Kali Linux penetration testing MCP server with sibling tools like ad_password_spray, ad_secretsdump, ad_psexec, and ad_kerberoast. Masscan is a high-speed port scanner capable of scanning the entire internet.
Documented attack patterns abuse exactly the kind of access tools_masscan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zebbern Kali MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for tools_masscan:
{
"version": "1",
"default": "deny",
"tools": {
"tools_masscan": {
"limits": [
{
"counter": "tools_masscan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}tools_masscan 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.
tools_masscan. It is categorised as a Execute tool in the Zebbern Kali MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zebbern Kali MCP server in PolicyLayer and add a rule for tools_masscan: 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 Zebbern Kali MCP. Nothing to install.
tools_masscan 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 tools_masscan 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 tools_masscan. 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.
tools_masscan is provided by the Zebbern Kali MCP server (zebbern/zebbern-kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 Zebbern Kali MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 Zebbern Kali MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.