快速端口扫描(仅端口扫描层)
AI agents invoke quick_scan to trigger actions in MCP Port Scanner. 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 is an active network operation that sends packets to external hosts to probe open ports. This constitutes execution of network-level operations with real effects on target systems. It can be considered reconnaissance/intrusive depending on context, and misuse could violate laws (unauthorized scanning) or trigger security alerts.
From the tool's definition '快速端口扫描' (quick port scan) - triggers external network scanning operations against target systems
Attacks that exploit this kind of access
快速端口扫描(仅端口扫描层). It is categorised as a Execute tool in the MCP Port Scanner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Port Scanner MCP server in PolicyLayer and add a rule for quick_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 MCP Port Scanner. Nothing to install.
quick_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 quick_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 quick_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.
quick_scan is provided by the MCP Port Scanner MCP server (relaxcloud-cn/mcp-port-scanner). 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 →