Start a feroxbuster directory scan against a target URL. Executes on remote Kali system via SSH.
AI agents invoke feroxbuster_scan to trigger actions in Feroxbuster. 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.
This tool executes an active web content discovery/enumeration scan against a target URL by running feroxbuster on a remote system via SSH. It triggers external operations (network scanning, directory brute-forcing) whose effects depend on the target URL and configuration arguments.
From the tool's definition 'Start a feroxbuster directory scan against a target URL. Executes on remote Kali system via SSH.'
Attacks that exploit this kind of access
Start a feroxbuster directory scan against a target URL. Executes on remote Kali system via SSH. It is categorised as a Execute tool in the Feroxbuster MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Feroxbuster 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 Feroxbuster. 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 Feroxbuster MCP server (schwarztim/sec-feroxbuster-mcp). 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 →