medusaFtpScan

medusaFtpScan

Server Linux Network Scanner MCP Server nibesh0/netsecmcp
Category Execute
Risk class High
Parameters 00 required

What medusaFtpScan does on Linux Network Scanner MCP Server

AI agents invoke medusaFtpScan to trigger actions in Linux Network Scanner MCP Server. 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 medusaFtpScan needs a policy

Medusa is a widely-recognized brute-force credential attack tool. 'medusaFtpScan' almost certainly runs Medusa against FTP targets to perform credential brute-forcing, which constitutes executing an active attack against external systems. This is an Execute/critical classification due to the offensive nature — it can compromise remote systems, and misuse could result in unauthorized access to FTP servers.

From the tool's definition Tool name 'medusaFtpScan' combined with sibling tool 'ftpBruteForce' and server context featuring offensive security tools (aircrackScan, exploitScan, bettercapScan). Medusa is a well-known parallel network login brute-forcer targeting FTP and other protocols.

Questions about medusaFtpScan

What does the medusaFtpScan tool do? +

medusaFtpScan. It is categorised as a Execute tool in the Linux Network Scanner MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on medusaFtpScan? +

Register the Linux Network Scanner MCP Server MCP server in PolicyLayer and add a rule for medusaFtpScan: 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 Linux Network Scanner MCP Server. Nothing to install.

What risk level is medusaFtpScan? +

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

Can I rate-limit medusaFtpScan? +

Yes. Add a rate_limit block to the medusaFtpScan 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 medusaFtpScan completely? +

Set action: deny in the PolicyLayer policy for medusaFtpScan. 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 medusaFtpScan? +

medusaFtpScan is provided by the Linux Network Scanner MCP Server MCP server (nibesh0/netsecmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.