Security Data Sheet

MCP Connector for Revit

Version 3.8.3, reviewed 12 October 2026.

What it does

A Revit add-in that lets your existing AI assistant read and edit the model that is open on the user's machine. You bring your own AI subscription. Supported on Revit 2022 to 2027.

How edits are controlled

The connector carries out calls from programs running under the same Windows account, normally your AI client. The connection must be switched on in Revit. Whether you approve each call is set in the AI client. The connector does not require a separate confirmation for every edit.

The free tier cannot create or delete model elements or change their parameters. Its tools query and report on the model, change the selection and the active view, and can hide or isolate elements in a view. Hiding is temporary unless the call asks for a permanent hide in that view, which can be undone.

Pro tools that modify the model run inside standard Revit transactions, so each change appears in the Revit undo history and can be reversed with Undo. A step that fails is rolled back rather than left half made. Tools that work through many items, such as purges, warning fixes and batch edits, can skip an item that fails, keep the rest and report what was skipped, and some of them record more than one undo step. Saving, synchronising, enabling worksharing and writing files cannot be undone.

Revit's normal interactive warning and error handling is the default. Supported modelling calls can instead request rollback on a warning, or accept only warnings identified explicitly in that call. Under this per-call policy, unlisted warnings and errors roll the transaction back; the policy does not automatically resolve errors. Replies report warnings and cancelled or rolled-back steps so completed work can be distinguished from work that was not saved.

The connector never saves, synchronises or relinquishes on its own. Those actions happen only through the tools whose purpose is to save, save as, compact, synchronise, relinquish, close or enable worksharing, and there is no autosave or timed synchronisation. The relinquish tool saves the local file first unless told not to. Family tools save family files only to a path named in the call, or back to the file the family was opened from. Worksharing permissions and element ownership apply to AI-driven changes exactly as they do to manual ones: the connector never takes ownership of another user's elements, and if a change touches one, Revit refuses it and the tool reports the failure.

Where model data goes

Tool results go to the AI application you connect. If it uses a cloud AI provider, project information is processed under your account settings and agreement with that provider. A local AI setup can keep inference on your own computer or server. Running the connector locally does not, by itself, make the AI processing local.

The add-in runs inside Revit on the workstation. The component that talks to your AI client has no third-party dependencies and makes no outbound network connections of its own.

Project files and outputs

The connector does not send model content or tool results to AUTOM8LABS. Your AI application controls what it sends to its provider. Files, images and reports requested through tools can contain project information and can be written to locations available to your Windows account, including network shares.

What AUTOM8LABS receives

Licence activation, validation and release Licence key, product code, a hashed machine identifier, the Windows machine name, the version number and a random session identifier. Installs with no licence make no licence-related connection at all.

The machine identifier is a SHA-256 hash of hardware identifiers, or of the machine and account names where Windows cannot supply them. The underlying values never leave the machine.

What is stored

Model contentNever received or stored
File names and pathsNever received or stored
Licence recordsLicence key, hashed machine identifier, machine name and client version. Held for the duration of the licence and deleted on request
Payment recordsStripe for website purchases, Autodesk for store purchases. AUTOM8LABS does not store card data

On the workstation

  • No listening port. The add-in communicates with your AI client over a Windows named pipe, not a network socket.
  • Access restricted to the same Windows user. On Revit 2025 and later the pipe is opened current-user-only, so Windows scopes it to the account Revit is running under. On Revit 2022 to 2024 the pipe carries a single access control entry for that same account, and if the account cannot be resolved no pipe is created. On every version the connector's bridge checks that the pipe belongs to that account before connecting. Any program running under that account can use the pipe.
  • No log file by default. Diagnostics are off unless a user sets an environment variable for troubleshooting. When enabled, the log records connector events and, in the most detailed mode, the start of each tool request, which can include model file paths, element identifiers and text. It never leaves the machine.
  • Stored credentials are encrypted. The licence cache, which also holds the pack entitlement, is protected with Windows DPAPI at machine scope, so a copy taken to another computer cannot be read. A key placed by IT for pre-deployment stays unencrypted until it is first validated.
  • Adds itself to AI apps. Switching the connection on registers the connector with each supported AI app found for that Windows user, including Codex inside WSL, which it reaches by running wsl.exe. Switching it off removes those entries. Each time Revit starts, the connector repairs its own entry if the path has moved, and changes nothing else in those files.
  • No elevated privileges are required at runtime. Installation needs administrator rights once.

Administrator controls

With Pro, an administrator can block tools by name or permit only an approved list. These restrictions apply when tools are listed and when a call is executed, including calls inside a batch. They restrict the licensed tools; they do not grant additional access. The controls are off unless configured.

Policies can be assigned by computer or by user through Group Policy or Intune using the supplied template. Where policies overlap, the stricter tool restrictions apply. An administrator can also force Read-Only Session; the user cannot turn that lock off in the connection dialog.

Read-Only Session blocks model-changing tools while retaining permitted queries, navigation and exports. It protects the Revit model; it does not prevent file exports or every change to the user interface.

Optional audit log

The optional Pro audit log is off by default. When an administrator enables it, the connector records tool calls, including refusals and batch steps. Records contain the Windows user and computer, host version, project name or path, AI app name, tool, outcome, duration and shortened arguments and error text. These fields can contain project information. Tool results are not copied into the audit log.

An administrator can also request a short reason from the AI for each call. This is the AI's account of the request, not a copy of the user's chat. Logs are written locally and can be copied to an administrator-selected folder or network share. Local audit files are retained for 90 days; retention and access at the destination are controlled by your organisation. AUTOM8LABS does not receive them.

Audit recording is best effort. A failed write or unavailable share does not block the tool, so the log is not a guaranteed or tamper-proof record.

Supply chain

All third-party components are widely used libraries from the official NuGet ecosystem. Every component declares a licence. All are MIT except one, which is Apache-2.0. There are no copyleft licences in the shipped product.

Dependency inventories cover the plug-in and its AI connection component, including the bundled runtime. CycloneDX SBOMs are available on request for this release. Release package checks on 12 October 2026 reported no known vulnerabilities in the dependencies checked. This is a dated check, not a guarantee against vulnerabilities discovered later.

SBOMs are available on request from [email protected].

Assurance

Every AUTOM8LABS binary and the installer are code-signed as AUTOM8LABS LTD through Azure Trusted Signing. Third-party libraries ship as their publishers release them.

See the Trust Center for the full assurance position and the sub-processor list.