对单个IP地址进行智能分层端口扫描
AI agents invoke scan_target 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 probes to external hosts, triggering real network traffic and potentially alerting intrusion detection systems. It is not a passive read — it executes external network actions whose effects depend on the target argument. Misuse by an AI agent could scan unauthorized hosts, constituting unauthorized access probing, hence high severity.
From the tool's definition '智能分层端口扫描' (intelligent layered port scan) on a single IP address; server is described as a 'port scanning service' for 'network security analysis'
Attacks that exploit this kind of access
对单个IP地址进行智能分层端口扫描. 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 scan_target: 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.
scan_target 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 scan_target 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 scan_target. 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.
scan_target 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 →