This record as markdown: /tools/seac-25-kali-security-mcp/feroxbuster-scan.md
What feroxbuster_scan does on Kali Security MCP
AI agents invoke feroxbuster_scan to trigger actions in Kali Security MCP. 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.
Why feroxbuster_scan is rated High
Feroxbuster is an active web reconnaissance tool that performs directory and resource brute-forcing against target web servers. It sends large volumes of HTTP requests to enumerate hidden paths and resources. This constitutes active execution of an external operation against a target system, making it Execute category.
From the tool's definition 使用 Feroxbuster 执行目录与资源爆破 (Execute directory and resource brute-forcing using Feroxbuster)
Attacks that exploit this kind of access
The rule that runs feroxbuster_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For feroxbuster_scan, this is the rule to start with:
feroxbuster_scan 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kali Security MCP, apply this rule, and every feroxbuster_scan call is checked against it from then on.
Questions about feroxbuster_scan
使用 Feroxbuster 执行目录与资源爆破。. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security MCP server in PolicyLayer and add a rule for feroxbuster_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 Security MCP. Nothing to install.
feroxbuster_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 feroxbuster_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 feroxbuster_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.
feroxbuster_scan is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kali Security, and thousands of servers like it.
Across the catalogue