Execute a multi-line script on a node. The script is written to a temp file and executed, keeping tool call display compact. Use this instead of omniwire_exec for Python scripts, heredocs, or any command >3 lines.
AI agents invoke omniwire_run 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 directly executes user-supplied code on remote nodes in a distributed system. Combined with the server's persistent SSH2 connection pooling and cross-node capabilities, a compromised or misdirected AI agent could execute destructive commands (deletes, data exfiltration), establish persistence, or pivot across infrastructure.
From the tool's definition Tool executes arbitrary multi-line scripts on nodes with no restrictions mentioned. Description states 'Execute a multi-line script on a node' and explicitly recommends use for 'Python scripts, heredocs, or any command >3 lines', enabling arbitrary code…
Documented attack patterns abuse exactly the kind of access omniwire_run 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_run:
{
"version": "1",
"default": "deny",
"tools": {
"omniwire_run": {
"limits": [
{
"counter": "omniwire_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}omniwire_run 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.
Execute a multi-line script on a node. The script is written to a temp file and executed, keeping tool call display compact. Use this instead of omniwire_exec for Python scripts, heredocs, or any command >3 lines. 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_run: 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_run 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_run 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_run. 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_run 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.