AI agents call ssh-keyscan to retrieve information from Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
ssh-keyscan is a standard utility that only reads/retrieves public SSH host keys from remote servers. It performs passive information gathering with no side effects, modifications, or command execution capability. This is a quintessential Read operation. Severity is low because public keys are by definition public, though the confidence is not perfect due to the truncated description.
From the tool's definition Tool name is 'ssh-keyscan' and description states 'Retrieves public host keys from a remote SSH server' — retrieval of public information with no modification or execution of commands on the remote system.
Attacks that exploit this kind of access
Retrieves public host keys from a remote SSH server using. It is categorised as a Read tool in the Python MCP Server, which means it retrieves data without modifying state.
Register the Python 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 Python. 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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ssh-keyscan is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →