AI agents invoke port_scan_nmap to trigger actions in SeldomMaster. 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.
Nmap is a network scanning tool that actively probes network hosts and services. Even with an empty description, the tool name 'port_scan_nmap' clearly indicates execution of nmap scans against network targets.
From the tool's definition Tool name 'port_scan_nmap' combined with server description mentioning 'local network hacking' and sibling tools like 'discover_neighbors_arp', 'discover_services_mdns' indicating active network reconnaissance
Documented attack patterns abuse exactly the kind of access port_scan_nmap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SeldomMaster, and nothing reaches the server without passing your rules. This is the rule we recommend for port_scan_nmap:
{
"version": "1",
"default": "deny",
"tools": {
"port_scan_nmap": {
"limits": [
{
"counter": "port_scan_nmap_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}port_scan_nmap 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.
port_scan_nmap. It is categorised as a Execute tool in the SeldomMaster MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SeldomMaster MCP server in PolicyLayer and add a rule for port_scan_nmap: 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 SeldomMaster. Nothing to install.
port_scan_nmap 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 port_scan_nmap 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 port_scan_nmap. 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.
port_scan_nmap is provided by the SeldomMaster MCP server (paralax/seldommonster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SeldomMaster, 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.
52 SeldomMaster tools catalogued and risk-classified — across an index of 43,000+ MCP servers.