omniwire_user

THE RISK

Critical Risk

Why omniwire_user needs a policy

This tool spans multiple severity levels but must be classified at the most severe. 'remove' (delete user accounts irreversibly), 'remove-key' (delete SSH keys), 'sudo-remove' (revoke sudo privileges) are destructive and potentially irreversible operations. 'sudo-add' grants elevated privileges on mesh nodes — a severe security risk if misused by an AI agent. 'passwd' can lock out legitimate users.

From the tool's definition Actions: list, add, remove, add-key, remove-key, sudo-add, sudo-remove, passwd

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

POLICY

How to control omniwire_user

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_user:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "omniwire_user"
  ]
}

omniwire_user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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_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. Execute omniwire_alias In-session command shortcuts. Set short aliases for long commands, then run them by alias

All 88 OmniWire tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in OmniWire → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about omniwire_user

What does the omniwire_user tool do? +

User and SSH key management on mesh nodes. Actions: list, add, remove, add-key, remove-key, sudo-add, sudo-remove, passwd. It is categorised as a Destructive tool in the OmniWire MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on omniwire_user? +

Register the OmniWire MCP server in PolicyLayer and add a rule for omniwire_user: 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_user? +

omniwire_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit omniwire_user? +

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

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

omniwire_user 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 →