List available wordlists on the Kali system
AI agents call feroxbuster_wordlists 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 performs a retrieval/enumeration of wordlist files available on the system. It has no side effects, does not execute scans, modify data, or trigger external operations. The action is purely informational, making it a Read category risk with low severity since listing wordlists poses minimal security risk even if an AI agent misuses it.
From the tool's definition Tool name and description indicate it 'List available wordlists' — a query operation that retrieves information about existing resources with no modification or execution of code.
Attacks that exploit this kind of access
List available wordlists on the Kali system. 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_wordlists: 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_wordlists 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_wordlists 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_wordlists. 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_wordlists 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 →