Get the results from the last completed scan
AI agents call feroxbuster_results 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 queries and returns previously generated scan results. It performs no side effects, does not execute commands, and does not modify or destroy data. While feroxbuster itself is a web content discovery tool that can identify sensitive endpoints, this particular tool is purely informational—it retrieves cached results from a prior scan.
From the tool's definition Tool description explicitly states 'Get the results from the last completed scan' — a retrieval operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get the results from the last completed scan. 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_results: 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_results 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_results 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_results. 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_results 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 →