ssh-keyscan
Retrieves public host keys from a remote SSH server using
This record as markdown: /tools/io-github-dave-london-http/ssh-keyscan.md
What ssh-keyscan does on Http
AI agents call ssh-keyscan to retrieve information from Http without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ssh-keyscan is rated Low
ssh-keyscan is a standard utility that passively retrieves public SSH host keys for verification purposes. It performs no write operations, does not execute commands, and cannot delete or modify data. While it does perform network reconnaissance, the blast radius is minimal as it only gathers already-public information. Classified as Read with low severity.
From the tool's definition Tool name is 'ssh-keyscan' and description states it 'Retrieves public host keys from a remote SSH server' — a read-only operation that queries public cryptographic material without modifying or executing anything on the target.
Attacks that exploit this kind of access
The rule that runs ssh-keyscan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Http, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh-keyscan, this is the rule to start with:
ssh-keyscan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Http, apply this rule, and every ssh-keyscan call is checked against it from then on.
Questions about ssh-keyscan
Retrieves public host keys from a remote SSH server using. It is categorised as a Read tool in the Http MCP Server, which means it retrieves data without modifying state.
Register the Http MCP server in PolicyLayer and add a rule for ssh-keyscan: 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 Http. Nothing to install.
ssh-keyscan 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-keyscan 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-keyscan. 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-keyscan is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Http, and thousands of servers like it.
This server
Across the catalogue