Get feroxbuster version information from Kali
AI agents call feroxbuster_version to retrieve information from Feroxbuster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns version information from the feroxbuster scanner. It performs a read-only query with no capability to modify, execute code, delete data, or initiate scans. The blast radius of misuse is minimal—an attacker gains only version information, which is typically public or easily discoverable through other means.
From the tool's definition Tool name 'feroxbuster_version' and description 'Get feroxbuster version information from Kali' indicate a query operation that retrieves version metadata with no side effects.
Attacks that exploit this kind of access
Get feroxbuster version information from Kali. It is categorised as a Read tool in the Feroxbuster MCP Server, which means it retrieves data without modifying state.
Register the Feroxbuster MCP server in PolicyLayer and add a rule for feroxbuster_version: 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_version is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the feroxbuster_version 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_version. 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_version 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 →