omniwire_sync_rules

THE RISK

Medium Risk

Why omniwire_sync_rules needs a policy

This tool synchronizes configuration files (rules and hooks) across all mesh nodes in a distributed infrastructure. Pushing rules/hooks to all nodes is a Write operation that modifies configuration across the entire mesh. The blast radius is high because it can overwrite behavioral rules and hooks on every connected node simultaneously, potentially altering how AI agents operate across the entire infrastructure.

From the tool's definition Sync Claude Code rules (CLAUDE.md, rules/*.md, hooks/*) bi-directionally across all mesh nodes. Push local rules to all nodes or pull latest from remote.

Documented attack patterns abuse exactly the kind of access omniwire_sync_rules gives an agent:

POLICY

How to control omniwire_sync_rules

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "omniwire_sync_rules": {
      "limits": [
        {
          "counter": "omniwire_sync_rules_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

omniwire_sync_rules stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register OmniWire — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OmniWire tools

Destructive cybersync_force_push Force push a specific file to all online nodes, overwriting remote copies. Destructive omniwire_2fa TOTP 2FA manager — add/generate/list/delete/verify/export 2FA secrets. Stores encrypted in Destructive omniwire_user User and SSH key management on mesh nodes. Actions: list, add, remove, add-key, remove-key Destructive omniwire_backup Snapshot and restore paths on mesh nodes. Creates timestamped tarballs in /var/backups/omn Execute omniwire_cdp Chrome DevTools Protocol — persistent headless browser via Docker container. Navigate, scr 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-mes Execute cybersync_sync_now Trigger immediate full reconciliation of all tool configs.

All 88 OmniWire tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about omniwire_sync_rules

What does the omniwire_sync_rules tool do? +

Sync Claude Code rules (CLAUDE.md, rules/*.md, hooks/*) bi-directionally across all mesh nodes. Push local rules to all nodes or pull latest from remote. It is categorised as a Write tool in the OmniWire MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on omniwire_sync_rules? +

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

What risk level is omniwire_sync_rules? +

omniwire_sync_rules is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit omniwire_sync_rules? +

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

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

omniwire_sync_rules is provided by the OmniWire MCP server (voidchecksum/omniwire). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OmniWire tool call.

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

CHECK YOUR STACK →