// SCAN REPORT

HomeOps MCP Server

7 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

2 can modify or destroy data

5 read-only

7 tools total

Community server · catalogue entry verified 03/07/2026

How to control HomeOps MCP Server ↓

TOOL MAP

What HomeOps MCP Server exposes to your agents

Read (5) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous HomeOps MCP Server tools

Execute · High docker_restart_container This tool executes a command against external infrastructure (Docker) that causes a state change in running services. Execute · Medium emby_scan_library This tool triggers an active operation (library scan) on an external media server.

2 of HomeOps MCP Server's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control HomeOps MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and HomeOps MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "docker_get_logs": {
    "limits": [
      {
        "counter": "docker_get_logs_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register HomeOps MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON HOMEOPS →

Instant setup, no code required.

FULL CATALOGUE

All 7 HomeOps MCP Server tools

EXECUTE 2 tools

Execute docker_restart_container Restart a Docker container by name. Execute emby_scan_library Trigger a library scan on the Emby media server.

READ 5 tools

Read docker_get_logs Get recent logs from a Docker container. Read docker_get_stats Get resource usage statistics for all running containers. Read docker_list_containers List Docker containers with their status. Read emby_get_sessions List active Emby playback sessions. Read emby_search_library Search the Emby media library.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about HomeOps MCP Server

Is the HomeOps MCP Server MCP server safe to use without restrictions? +

The HomeOps MCP Server server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the HomeOps MCP Server MCP server expose? +

7 tools across 2 categories: Execute, Read. 5 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on HomeOps MCP Server? +

Register the HomeOps MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every HomeOps MCP Server tool call.

Deterministic rules across all 7 HomeOps MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HOMEOPS →

Instant setup, no code required.

7 HomeOps MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.