Remote Tool Execution Proxy

One Mind Across Every Machine · Shipped · workstation, home

Run tools on a peer machine from the primary dashboard — results return through the authenticated channel.

The peer tool proxy allows the agent on the Canonical Host to invoke MCP tools on any paired satellite. This enables scenarios like running GPU diagnostics on a remote workstation or checking sensor data on a Raspberry Pi — all from the primary dashboard.

The proxy routes MCP tool calls (tools/list, tools/call) to the paired peer’s MCP server over HTTP JSON-RPC 2.0. Authentication uses the per-peer bearer token established during pairing. Results are returned to the host agent’s turn context.

Limits and invariants

Remote tool calls are subject to the same approval policies as local calls — no privilege escalation through federation.

Where this lives

• halbert_core/halbert_core/agents/peer_tool_proxy.py