Scan a network/IP range and enumerate smb shares. If mulitple targets are provided and they are not in CIDR format, they should be space-separated.
AI agents invoke smb_share_enum_scan to trigger actions in Nmap. 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 network reconnaissance by running Nmap SMB share enumeration against remote hosts. It is not a passive read — it sends network packets to external systems and triggers SMB protocol interactions.
From the tool's definition 'Scan a network/IP range and enumerate smb shares' — actively probes remote systems using Nmap SMB enumeration scripts against potentially multiple targets
Documented attack patterns abuse exactly the kind of access smb_share_enum_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nmap, and nothing reaches the server without passing your rules. This is the rule we recommend for smb_share_enum_scan:
{
"version": "1",
"default": "deny",
"tools": {
"smb_share_enum_scan": {
"limits": [
{
"counter": "smb_share_enum_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} smb_share_enum_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.
Scan a network/IP range and enumerate smb shares. If mulitple targets are provided and they are not in CIDR format, they should be space-separated. It is categorised as a Execute tool in the Nmap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nmap MCP server in PolicyLayer and add a rule for smb_share_enum_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 Nmap. Nothing to install.
smb_share_enum_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 smb_share_enum_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 smb_share_enum_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.
smb_share_enum_scan is provided by the Nmap MCP server (jarrodcoulter/nmap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nmap, 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.
5 Nmap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.