get_host_facts

Get safe host metadata (OS, uptime, kernel) — no secrets.

SERVERSSH MCP Server SOURCEbhayanak/ssh-mcp-server

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/bhayanak-ssh-mcp-server/get-host-facts.md

WHAT IT DOES

What get_host_facts does on SSH MCP Server

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

RISK

Why get_host_facts is rated Low

This tool performs a read-only query of host metadata without modifying state, executing code, or accessing sensitive data. The blast radius of misuse is minimal—an attacker gains only basic system information already typically discoverable through reconnaissance. Low severity reflects the non-sensitive nature of the data returned.

From the tool's definition Description states 'Get safe host metadata (OS, uptime, kernel) — no secrets.' The tool retrieves information only, with explicit confirmation that secrets are excluded.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_host_facts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_host_facts, this is the rule to start with:

get_host_facts Allowed

get_host_facts 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": {
    "get_host_facts": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every get_host_facts call is checked against it from then on.

FAQ

Questions about get_host_facts

What does the get_host_facts tool do? +

Get safe host metadata (OS, uptime, kernel) — no secrets. It is categorised as a Read tool in the SSH MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_host_facts? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for get_host_facts: 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. Nothing to install.

What risk level is get_host_facts? +

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

Can I rate-limit get_host_facts? +

Yes. Add a rate_limit block to the get_host_facts 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 get_host_facts completely? +

Set action: deny in the PolicyLayer policy for get_host_facts. 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 get_host_facts? +

get_host_facts is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SSH MCP Server, and thousands of servers like it.

This server

All 23 SSH MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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