AI agents call zeek_ssh_bruteforce to retrieve information from Zeek without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs log analysis and pattern detection over Zeek security monitoring data to surface suspicious SSH activity. It retrieves and correlates existing log entries to identify potential threats but does not modify logs, delete data, execute code on systems, or trigger external operations.
From the tool's definition Tool description states it "Detect[s] SSH brute force attempts by identifying sources with multiple failed authentication attempts exceeding a threshold." This is a detection and analysis operation that queries and identifies patterns in network security logs…
Attacks that exploit this kind of access
Detect SSH brute force attempts by identifying sources with multiple failed authentication attempts exceeding a threshold. It is categorised as a Read tool in the Zeek MCP Server, which means it retrieves data without modifying state.
Register the Zeek MCP server in PolicyLayer and add a rule for zeek_ssh_bruteforce: 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 Zeek. Nothing to install.
zeek_ssh_bruteforce 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 zeek_ssh_bruteforce 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 zeek_ssh_bruteforce. 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.
zeek_ssh_bruteforce is provided by the Zeek MCP server (solomonneas/zeek-mcp). 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 →