Query failed SSH connection attempts from the log. Filter by time period or custom date range.
AI agents call ssh_failed_connections to retrieve information from Ssh Mcp Server Secured without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves historical log data about failed connection attempts. It does not execute commands, modify data, delete records, or trigger any external operations. The filtering by time period or date range is performed on already-existing log data without any alterations.
From the tool's definition Tool description states 'Query failed SSH connection attempts from the log' - this is a retrieval/query operation with no side effects. The verb 'Query' and the action of reading log data indicates read-only access.
Attacks that exploit this kind of access
Query failed SSH connection attempts from the log. Filter by time period or custom date range. It is categorised as a Read tool in the Ssh Mcp Server Secured MCP Server, which means it retrieves data without modifying state.
Register the Ssh Mcp Server Secured MCP server in PolicyLayer and add a rule for ssh_failed_connections: 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 Ssh Mcp Server Secured. Nothing to install.
ssh_failed_connections 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 ssh_failed_connections 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 ssh_failed_connections. 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.
ssh_failed_connections is provided by the Ssh Mcp Server Secured MCP server (marian-craciunescu/ssh-mcp-server-secured). 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 →