ssh-keyscan

Retrieves public host keys from a remote SSH server using

SERVERBuild SOURCEDave-London/Pare

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/ssh-keyscan.md

WHAT IT DOES

What ssh-keyscan does on Build

AI agents call ssh-keyscan to retrieve information from Build without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ssh-keyscan is rated Low

ssh-keyscan performs a passive read operation that obtains public cryptographic key material from SSH servers. This is a standard reconnaissance activity that does not modify data, execute code, or cause side effects on the target system. Public host keys are non-sensitive data by design.

From the tool's definition Tool name is 'ssh-keyscan' and description states 'Retrieves public host keys from a remote SSH server'. The verb 'retrieves' and 'public host keys' indicate read-only data collection without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ssh-keyscan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, 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 Allowed

ssh-keyscan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh-keyscan": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every ssh-keyscan call is checked against it from then on.

FAQ

Questions about ssh-keyscan

What does the ssh-keyscan tool do? +

Retrieves public host keys from a remote SSH server using. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ssh-keyscan? +

Register the Build 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 Build. Nothing to install.

What risk level is ssh-keyscan? +

ssh-keyscan is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ssh-keyscan? +

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.

How do I block ssh-keyscan completely? +

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.

What MCP server provides ssh-keyscan? +

ssh-keyscan is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →