ping_host · Homelab MCP: Risk & Policy

WHAT IT DOES

What ping_host does on Homelab

AI agents invoke ping_host to trigger actions in Homelab. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why ping_host needs a policy

Pinging a host via Ansible involves executing a network operation (ICMP or Ansible ping module) against a remote host. This is more than a passive read — it triggers an external operation on a target system. While the blast radius is moderate (it could expose network topology or trigger unintended Ansible actions), it doesn't write or destroy data.

From the tool's definition Ping a specific host by hostname from Ansible inventory

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ping_host Rate-limited

ping_host stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ping_host": {
      "limits": [
        {
          "counter": "ping_host_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Homelab, so you can run agents against it safely.

FAQ

Questions about ping_host

What does the ping_host tool do? +

Ping a specific host by hostname from Ansible inventory. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ping_host? +

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

What risk level is ping_host? +

ping_host is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ping_host? +

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

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

ping_host is provided by the Homelab MCP server (myraffy/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.