Configure default feroxbuster settings for subsequent scans
AI agents use feroxbuster_config to create or update resources in Feroxbuster — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Feroxbuster environment.
This tool creates or modifies configuration data reversibly. While it doesn't directly delete data or execute scans itself, it changes settings that will be applied to future scans. This is a Write-category action because configuration changes are typically reversible (can be reconfigured).
From the tool's definition Tool enables configuration of 'default feroxbuster settings for subsequent scans', which modifies state that affects subsequent operations.
Attacks that exploit this kind of access
Configure default feroxbuster settings for subsequent scans. It is categorised as a Write tool in the Feroxbuster MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Feroxbuster MCP server in PolicyLayer and add a rule for feroxbuster_config: 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_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the feroxbuster_config 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_config. 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_config 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 →