In-session command shortcuts. Set short aliases for long commands, then run them by alias name on any node.
AI agents invoke omniwire_alias to trigger actions in OmniWire. 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.
This tool facilitates Execute-class behavior: it runs code/commands on remote infrastructure nodes. Although the tool itself only creates shortcuts, those shortcuts ultimately trigger command execution on any node in the mesh. The distributed, multi-node execution context and SSH2 pooling elevate the blast radius from a simple Write action to Execute.
From the tool's definition Tool enables running commands by alias name on any node across distributed infrastructure. The server description states it provides 'AI agents to execute commands...across multiple nodes' and features 'persistent SSH2 connection pooling.' The alias mechanism…
Documented attack patterns abuse exactly the kind of access omniwire_alias gives an agent:
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_alias:
{
"version": "1",
"default": "deny",
"tools": {
"omniwire_alias": {
"limits": [
{
"counter": "omniwire_alias_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}omniwire_alias 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.
Free to start. No card required.
In-session command shortcuts. Set short aliases for long commands, then run them by alias name on any node. It is categorised as a Execute tool in the OmniWire MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OmniWire MCP server in PolicyLayer and add a rule for omniwire_alias: 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.
omniwire_alias is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the omniwire_alias 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.
Set action: deny in the PolicyLayer policy for omniwire_alias. 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.
omniwire_alias 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.
Start from OmniWire, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 OmniWire tools catalogued and risk-classified — across an index of 43,000+ MCP servers.