OmniWire

88 tools. 65 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

65 can modify or destroy data
23 read-only
88 tools total

Community server · catalogue entry verified 12/06/2026

How to control OmniWire ↓

What OmniWire exposes to your agents

Read (23) Write / Execute (61) Destructive / Financial (4)
Critical Risk

The most dangerous OmniWire tools

65 of OmniWire's 88 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control OmniWire

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

Deny destructive operations
{
  "cybersync_force_push": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "omniwire_alert": {
    "limits": [
      {
        "counter": "omniwire_alert_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "omniwire_trace": {
    "limits": [
      {
        "counter": "omniwire_trace_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register OmniWire — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON OMNIWIRE →

Free to start. No card required.

All 88 OmniWire tools

EXECUTE 41 tools
Execute omniwire_cdp Chrome DevTools Protocol — persistent headless browser via Docker container. Navigate, screenshot, HTML, PDF, Execute omniwire_cron Manage cron jobs on a node. List, add, or remove scheduled tasks. Execute omniwire_omnimesh OmniMesh — built-in WireGuard mesh network manager. Create, manage, and monitor a full-mesh or hub-spoke WireG Execute cybersync_sync_now Trigger immediate full reconciliation of all tool configs. Execute omniwire_alias In-session command shortcuts. Set short aliases for long commands, then run them by alias name on any node. Execute omniwire_batch Run multiple commands in a single tool call. Supports chaining (sequential with {{prev}} interpolation), abort Execute omniwire_broadcast Execute a command on all online mesh nodes simultaneously. Execute omniwire_container Full Docker container lifecycle management. Actions: compose-up, compose-down, build, push, logs, ps, prune, s Execute omniwire_docker Run docker commands on a node. Default: contabo. Execute omniwire_exec Execute a command on a mesh node. Set background=true for async. Set via_vpn to route through VPN (Mullvad/Ope Execute omniwire_git Run git commands on a repository on any node. Execute omniwire_healthcheck Run a comprehensive health check across all nodes. Returns structured per-node status with connectivity, disk, Execute omniwire_log_aggregate Cross-node log search and aggregation. Run grep/journalctl across all nodes in parallel, merge results with no Execute omniwire_pipeline Execute a multi-step pipeline across nodes. Each step can depend on previous step output. Steps run sequential Execute omniwire_proxy HTTP/SOCKS proxy management on mesh nodes. Start HTTP proxies, SOCKS tunnels via SSH -D, or socat TCP forwarde Execute omniwire_run Execute a multi-line script on a node. The script is written to a temp file and executed, keeping tool call di Execute omniwire_shell Run a sequence of commands in a persistent shell session (preserves cwd, env vars). Execute omniwire_snippet Saved command templates on a node. Save reusable snippets with {{var}} placeholders, then run them with variab Execute omniwire_workflow Define and execute a named workflow (DAG of steps) that can be reused. Workflows are stored on disk and can be Execute omniwire_agent_task Dispatch a task to a specific node for background execution and retrieve results later. Creates a task file on Execute omniwire_benchmark Node performance benchmarking. CPU, memory, disk I/O, and network throughput. Actions: cpu, memory, disk, netw Execute omniwire_cert TLS certificate management. List, issue via certbot, renew, check expiry, inspect cert details, or generate se Execute omniwire_firewall Firewall engine for mesh nodes. Hardens external-facing security while keeping mesh traffic at full speed. Use Execute omniwire_kernel Kernel-level operations: dmesg, sysctl, modprobe, lsmod, strace, perf. Execute omniwire_mesh_expose Expose localhost-bound services to the entire WireGuard/Tailscale mesh. Makes any 127.0.0.1 service reachable Execute omniwire_mesh_gateway Auto-expose all localhost services across the mesh with a single command. Discovers localhost-only services on Execute omniwire_network Network diagnostics: ping, traceroute, dns lookup, open ports, bandwidth test. Execute omniwire_semaphore Distributed locking / semaphore for multi-agent coordination. Prevents race conditions when multiple agents op Execute omniwire_service_control Control systemd services on a node. Execute omniwire_stream Capture streaming command output (for tail -f, watch, etc.) for a limited duration. Execute omniwire_sync_hooks Sync Claude Code hooks (hooks/) bi-directionally across all mesh nodes. Execute omniwire_task_queue Distributed task queue for agent swarms. Producers enqueue tasks, consumer agents dequeue and process them. Su Execute omniwire_watch Poll a command until a condition is met or timeout. Useful for waiting on deployments, services starting, buil Execute omniwire_dns DNS management on mesh nodes. Resolve hostnames, switch DNS servers, flush caches, manage /etc/hosts entries. Execute omniwire_install_package Install a package on a node via apt, npm, or pip. Execute omniwire_open_browser Open a URL in a browser. Default: thinkpad (has GPU + display). Execute omniwire_port_forward Create SSH port forward tunnels to mesh nodes. Supports mesh-wide exposure: any tunnel can be made accessible Execute omniwire_schedule Distributed cron scheduling with failover. Stores schedule JSON, writes crontab entries on preferred node, sup Execute omniwire_scrape Scrape web pages using Scrapling via OmniMesh. Modes: http (TLS-spoofed, ~200ms), browser (Playwright JS rende Execute omniwire_update Check for updates, self-update OmniWire, manage auto-updates, and push updates to all mesh nodes. Sources: npm Execute omniwire_vpn Manage VPN on mesh nodes (Mullvad/OpenVPN/WireGuard/Tailscale). Mesh-safe: split-tunnel or namespace isolation
WRITE 20 tools
Write omniwire_alert Threshold alerting for mesh nodes. Fire when disk/mem/load exceeds threshold or service goes down. Destination Write omniwire_blackboard Shared blackboard for multi-agent collaboration. Agents post findings, hypotheses, and decisions to topic-scop Write omniwire_deploy Deploy a file from one node to multiple destination nodes. Write omniwire_transfer_file Copy a file or directory between mesh nodes using fast TCP transfer (netcat/tar or aria2c). Write omniwire_agent_registry Register/discover agents on the mesh. Agents announce their capabilities and other agents can discover them. E Write omniwire_clipboard Copy text between nodes via a shared clipboard buffer. Write omniwire_coc COC (CyberBase + Obsidian + Canvas) — unified sync. Default: writes to PostgreSQL, Obsidian vault (.md), and C Write omniwire_event Publish/subscribe events for agent coordination. Agents can emit events and other agents can poll for them. Ev Write omniwire_knowledge CyberBase knowledge base — CRUD, search, and health management for the unified PostgreSQL knowledge store. Aut Write omniwire_store Key-value store for chaining results. Auto-persists to CyberBase. On get, checks memory first then CyberBase f Write omniwire_sync Bi-directional sync of rules, hooks, memory, agent configs, and settings across all mesh nodes. Syncs Claude C Write omniwire_sync_agents Sync agent configs (agents/, skills/) for Claude Code, OpenClaw, and other AI tools across all mesh nodes. Write omniwire_sync_memory Sync Claude Code memory files (memory/) bi-directionally across all mesh nodes. Write omniwire_sync_rules Sync Claude Code rules (CLAUDE.md, rules/.md, hooks/) bi-directionally across all mesh nodes. Push local rules Write cybersync_cookies Manage browser cookies across mesh nodes with CyberBase persistence. Store/retrieve/import/export in json/head Write omniwire_a2a_message Agent-to-agent messaging via shared message queues on mesh nodes. Agents can send/receive typed messages, enab Write omniwire_env Get or set environment variables on a node (persistent via /etc/environment). Write omniwire_events Event bus with Webhook + WebSocket + SSE support. Publish events, manage webhooks, query event log. All transp Write omniwire_secrets Manage secrets across mesh nodes. Supports 1Password, file-based, and env backends. Write omniwire_write_file Write/create a file on any mesh node. Default: contabo.
READ 23 tools
Read omniwire_trace Distributed tracing across mesh nodes. Start a trace, record spans with timing, view a waterfall breakdown of Read cybersync_diff Show items that differ between local node and the sync database. Read cybersync_get_memory Get Claude memory entries from PostgreSQL (ingested from memory.db). Read cybersync_history Query sync event history. Read cybersync_manifest Show what files are tracked per AI tool. Read cybersync_search_knowledge Search the unified knowledge base across all AI tools and nodes. Read cybersync_status CyberSync status: item counts, pending syncs, last heartbeat per node. Read omniwire_audit View and search the command audit log. All omniwire_exec calls are automatically logged. Supports viewing rece Read omniwire_capability Query node capabilities for intelligent task routing. Returns what tools, runtimes, and resources each node ha Read omniwire_cookies Cookie management across mesh nodes. Import/export/convert between JSON, Header string, and Netscape cookies.t Read omniwire_disk_usage Show disk usage across mesh nodes. Read omniwire_doctor Full health diagnostic for mesh nodes. Checks SSH connectivity, disk, memory, load, Docker, nftables, WireGuar Read omniwire_find_files Search for files across mesh nodes by name pattern. Read omniwire_list_files List files in a directory on any mesh node. Read omniwire_live_monitor Watch system metrics across all nodes (snapshot). Read omniwire_mesh_status Get health and resource usage for all mesh nodes. Read omniwire_metrics Collect and export Prometheus-compatible metrics from mesh nodes. Scrape returns current values; export format Read omniwire_node_info Get detailed information about a specific node. Read omniwire_plugin Plugin system loader. Scan and inspect JS plugin files in /etc/omniwire/plugins/ or ~/.omniwire/plugins/ on an Read omniwire_process_list List processes across mesh nodes, optionally filtered. Read omniwire_read_file Read a file from any mesh node. Default node: contabo (storage). Read omniwire_syslog Query system logs via journalctl on a node. Read omniwire_tail_log Read the last N lines of a log file on a node.

Related servers

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

Questions about OmniWire

Can an AI agent delete data through the OmniWire MCP server? +

Yes. The OmniWire server exposes 4 destructive tools including cybersync_force_push, omniwire_2fa, omniwire_user. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through OmniWire? +

The OmniWire server has 20 write tools including omniwire_alert, omniwire_blackboard, omniwire_deploy. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach OmniWire.

How many tools does the OmniWire MCP server expose? +

88 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 23 are read-only. 65 can modify, create, or delete data.

How do I enforce a policy on OmniWire? +

Register the OmniWire 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 OmniWire tool call.

Deterministic rules across all 88 OmniWire tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

88 OmniWire 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.