detect_ssh_brute_force
AI agents call detect_ssh_brute_force to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to identify or report on SSH brute-force attempts through analysis or querying of network/security data. This is a monitoring/detection capability with no direct side effects on network state or devices. While the description is empty (lowering confidence), the name strongly suggests a Read operation that retrieves security event information.
From the tool's definition Tool name 'detect_ssh_brute_force' indicates detection/monitoring of security events. The 'detect' prefix suggests querying or analyzing logs/metrics rather than taking direct action. No description provided.
Attacks that exploit this kind of access
detect_ssh_brute_force. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for detect_ssh_brute_force: 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 API-Central. Nothing to install.
detect_ssh_brute_force is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the detect_ssh_brute_force 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 detect_ssh_brute_force. 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.
detect_ssh_brute_force is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →