Low Risk

ssh-keyscan

Retrieves public host keys from a remote SSH server using

How to control ssh-keyscan ↓

What ssh-keyscan does on Make

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

Low Risk

Why ssh-keyscan needs a policy

ssh-keyscan fetches/reads public SSH host keys from remote servers — a read/query operation with no data modification. However, it involves outbound network connections to arbitrary remote hosts, which could be misused for network reconnaissance, hence medium severity rather than low.

From the tool's definition Retrieves public host keys from a remote SSH server using

Documented attack patterns abuse exactly the kind of access ssh-keyscan gives an agent:

How to control ssh-keyscan

PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh-keyscan:

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

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

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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 Make MCP Server, which means it retrieves data without modifying state.

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

Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Make tool call.

Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.