run_sync_bridge_flush

Open the outbound websocket bridge, pair or resume the local device, and flush pending approved operations to the paired web account.

SERVERNodebench SOURCEnodebench-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/run-sync-bridge-flush.md

WHAT IT DOES

What run_sync_bridge_flush does on Nodebench

AI agents invoke run_sync_bridge_flush to trigger actions in Nodebench. 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.

RISK

Why run_sync_bridge_flush is rated High

This tool executes operations with external side effects (opening websocket bridges, pairing devices, flushing pending operations). The outcome depends on runtime state (what operations are pending), making it Execute rather than Write. The 'high' severity reflects potential for unintended device pairing, connection hijacking, or execution of queued operations an AI agent did not authorize.

From the tool's definition Tool description includes 'Open the outbound websocket bridge', 'pair or resume the local device', and 'flush pending approved operations' — these are external operations that establish connections, manage device state, and trigger queued actions whose…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_sync_bridge_flush safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_sync_bridge_flush, this is the rule to start with:

run_sync_bridge_flush Rate-limited

run_sync_bridge_flush 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_sync_bridge_flush": {
      "limits": [
        {
          "counter": "run_sync_bridge_flush_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every run_sync_bridge_flush call is checked against it from then on.

FAQ

Questions about run_sync_bridge_flush

What does the run_sync_bridge_flush tool do? +

Open the outbound websocket bridge, pair or resume the local device, and flush pending approved operations to the paired web account. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_sync_bridge_flush? +

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

What risk level is run_sync_bridge_flush? +

run_sync_bridge_flush is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_sync_bridge_flush? +

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

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

run_sync_bridge_flush is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →