unicornscan_scan
AI agents invoke unicornscan_scan to trigger actions in Kali Linux MCP Server. 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.
Unicornscan is a well-known network scanning and reconnaissance tool in Kali Linux. Given the server context (penetration testing, network scanning) and the tool's name referencing unicornscan, it almost certainly performs active network scanning against target hosts. This is an Execute-category action as it triggers external network operations.
From the tool's definition Tool name 'unicornscan_scan' on a Kali Linux penetration testing server exposing 60+ security tools including 'network scanning' capabilities. Empty description.
Attacks that exploit this kind of access
unicornscan_scan. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for unicornscan_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 Kali Linux MCP Server. Nothing to install.
unicornscan_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 unicornscan_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 unicornscan_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.
unicornscan_scan is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). 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 →