ftpBruteForce
AI agents invoke ftpBruteForce 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.
A brute-force attack tool actively executes repeated authentication attempts against FTP servers to guess credentials. Even though the description is empty, the tool name 'ftpBruteForce' unambiguously describes an offensive security operation that executes credential-stuffing/brute-force attacks.
From the tool's definition Tool name 'ftpBruteForce' combined with server context of network security scanning tools including 'exploitScan', 'aircrackScan', 'bettercapScan', and 'directCmd'. The name explicitly indicates brute-force credential attack against FTP services.
Attacks that exploit this kind of access
ftpBruteForce. 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.
Register the Linux Network Scanner MCP Server MCP server in PolicyLayer and add a rule for ftpBruteForce: 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.
ftpBruteForce is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ftpBruteForce 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 ftpBruteForce. 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.
ftpBruteForce 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.
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 →