sshBruteForce
AI agents invoke sshBruteForce 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.
SSH brute force attacks execute credential-stuffing or password-guessing operations against remote SSH services. This is an active offensive action that can compromise systems, cause account lockouts, and violate authorization boundaries. The tool name unambiguously describes a brute-force attack capability.
From the tool's definition Tool name 'sshBruteForce' on a server with sibling tools including 'ftpBruteForce', 'exploitScan', 'aircrackScan', and 'directCmd' — all offensive security tools. Brute force attacks involve repeatedly executing authentication attempts against an SSH service.
Attacks that exploit this kind of access
sshBruteForce. 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 sshBruteForce: 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.
sshBruteForce 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 sshBruteForce 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 sshBruteForce. 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.
sshBruteForce 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 →