feroxbuster_scan

A execute tool on the Nyxstrike MCP server.

SERVERNyxstrike SOURCECommonHuman-Lab/nyxstrike
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nyxstrike/feroxbuster-scan.md

What feroxbuster_scan does on Nyxstrike

AI agents invoke feroxbuster_scan to trigger actions in Nyxstrike. 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.

Why feroxbuster_scan is rated High

Feroxbuster is a well-known fast content discovery/web enumeration tool used in offensive security. It actively scans web servers by sending HTTP requests to discover hidden directories and files. The empty description lowers confidence slightly, but the tool name clearly identifies it as an active scanning tool.

From the tool's definition Tool name 'feroxbuster_scan' combined with server context of 'AI Powered penetration testing Platform for offensive security research' and sibling tools including reconnaissance, payload generation, and attack suite tools.

Questions about feroxbuster_scan

What does the feroxbuster_scan tool do? +

feroxbuster_scan is a execute tool on the Nyxstrike MCP server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on feroxbuster_scan? +

Register the Nyxstrike 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 Nyxstrike. Nothing to install.

What risk level is feroxbuster_scan? +

feroxbuster_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit feroxbuster_scan? +

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.

How do I block feroxbuster_scan completely? +

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.

What MCP server provides feroxbuster_scan? +

feroxbuster_scan is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Nyxstrike, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nyxstrike's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.