// SCAN REPORT

PyNet Bridge

19 tools. 11 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

11 can modify or destroy data

8 read-only

19 tools total

Community server · catalogue entry verified 29/06/2026

How to control PyNet Bridge ↓

TOOL MAP

What PyNet Bridge exposes to your agents

Read (8) Write / Execute (9) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous PyNet Bridge tools

Destructive · High delete_pynet_module This tool irreversibly removes data (a module and all associated contents) with no undo mechanism. Destructive · High delete_script_button This tool performs an irreversible delete operation on a ScriptButton resource identified by Id. Execute · Low configure_output_window This tool triggers a UI state change (show/hide a window) in the PyNet platform. Execute · High send_command This tool directly executes scripts in the PyNet engine targeting a specific process by PID.

11 of PyNet Bridge's 19 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control PyNet Bridge

PolicyLayer is an MCP gateway — it sits between your AI agents and PyNet Bridge, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_pynet_module": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_pynet_module": {
    "limits": [
      {
        "counter": "create_pynet_module_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_plugin_status": {
    "limits": [
      {
        "counter": "check_plugin_status_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register PyNet Bridge — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PYNET BRIDGE →

Instant setup, no code required.

FULL CATALOGUE

All 19 PyNet Bridge tools

DESTRUCTIVE 2 tools

Destructive delete_pynet_module Permanently deletes a module and all its contents. Destructive delete_script_button Permanently removes a ScriptButton from a module by Id.

EXECUTE 5 tools

Execute configure_output_window Toggles the visibility of the PyNet log/output window. Execute send_command Direct script execution in the PyNet engine (Target PID, Script Name, Content). Execute send_command_by_path Executes a script file directly by path in the PyNet engine, without sending content inline. Execute viewer_fit Fits the camera to all models in the open viewer. Execute viewer_highlight_clash Highlights a clash pair in the open viewer by pnt_id (element A red, element B green).

WRITE 4 tools

Write create_pynet_module Creates a new custom Tab (ButtonsModule) in the Ribbon. Write deploy_script_button Installs a new ScriptButton into a specific module (Name, Script, Icon, Tooltip). Write update_script_button Updates metadata for an existing ScriptButton or moves it to another module. Write viewer_clear Clears highlights and ghosting in the open viewer.

READ 8 tools

Read check_plugin_status Handshake ping to verify the plugin listener is responsive. Read get_buttons_data Lists all script buttons for a specific module ID. Read get_output_window_status Checks if the output window is currently available/visible. Read get_pynet_ui_layout Fetches the full UI structure (ButtonsModules and ScriptButtons). Read list_active_instances Scans the system for running Autodesk processes with an active PyNet IPC pipe. Read viewer_list_clashes Reads the loaded package's clashes.json — the data source, NOT the viewer/IFC. Read viewer_load_package Loads a .pnt into the open viewer and returns a summary read from clashes.json. Read viewer_status Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir).

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about PyNet Bridge

Can an AI agent delete data through the PyNet Bridge MCP server? +

Yes. The PyNet Bridge server exposes 2 destructive tools including delete_pynet_module, delete_script_button. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through PyNet Bridge? +

The PyNet Bridge server has 4 write tools including create_pynet_module, deploy_script_button, update_script_button. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach PyNet Bridge.

How many tools does the PyNet Bridge MCP server expose? +

19 tools across 4 categories: Destructive, Execute, Read, Write. 8 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on PyNet Bridge? +

Register the PyNet Bridge MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every PyNet Bridge tool call.

Deterministic rules across all 19 PyNet Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PYNET BRIDGE →

Instant setup, no code required.

19 PyNet Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.