AI agents invoke net_port_scan to trigger actions in LuzzyTool. 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.
Port scanning actively sends network probes to external hosts to detect open TCP ports. This is an active network operation with side effects — it triggers connections to potentially arbitrary remote hosts. It is not a simple read of local data; it executes network reconnaissance. Misuse could target unauthorized systems, making severity high.
From the tool's definition TCP 端口扫描,检测目标主机指定端口是否开放 (TCP port scan, detect whether specified ports on target host are open)
Attacks that exploit this kind of access
【网络诊断】TCP 端口扫描,检测目标主机指定端口是否开放。. It is categorised as a Execute tool in the LuzzyTool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for net_port_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 LuzzyTool. Nothing to install.
net_port_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 net_port_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 net_port_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.
net_port_scan is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →