MCP Standard Tools 3.0.0: Apps and Access Rules

MCP Standard Tools SuiteApp version 3.0.0 adds File Cabinet apps and tools, runtime session information, and record transformation enhancements. File reads, uploads, and replacements require configured folder access alongside role permissions. That folder configuration does not filter listings, file-name searches, path lookups, or record attachments—a distinction administrators should review before rollout.

What's New in MCP Standard Tools?

The update covers three areas: interactive File Cabinet apps and supporting tools, a runtime session tool for inspecting the AI client connection, and record tools that identify and perform supported transformations. These capabilities support file handling, connection-context checks, and creating new records from existing records.

For broader release planning, see the NetSuite 2026.2 documentation updates. The sections below focus on the capabilities and access boundaries documented for MCP Standard Tools SuiteApp version 3.0.0.

What Can the File Cabinet MCP Apps Do?

The File Cabinet MCP Apps provide interactive interfaces for browsing folders, searching file names, uploading files, and sending supported file contents to the conversation. The three apps offer different entry points depending on whether the user needs to browse, retrieve a known file, or upload files.

For a known file, prepare its complete File Cabinet path before using Get File. For exploratory work, the Browser app provides folder navigation and file-name search. Supported contents is an important qualification: do not assume every File Cabinet file can be sent to a conversation. The source does not identify supported formats.

How Are Uploads and Replacements Handled?

Uploads through the File Cabinet Browser and Upload File apps retain the files' original names. When the destination folder already contains a file with the same name, click Replace Existing File to confirm replacement.

These are not the complete replacement requirements: the available upload documentation cuts off during an additional condition. Before relying on replacements, check the complete requirements and test with a noncritical file. Do not assume matching names and sufficient permissions are the only conditions.

How Does Allowed File Cabinet Access Work?

A user with the Administrator role must configure Allowed File Cabinet Access on the Custom Tools page before the apps can read, upload, or replace files. An empty allowed-folder list blocks all three operations. The configured access levels work alongside existing NetSuite role permissions; they do not override them.

Treat this as a two-part access review: check the allowed-folder configuration and the user's underlying role permissions. An allowed folder configured at View does not meet the documented minimum for uploading a new file. Likewise, configured folder access does not grant permissions missing from the NetSuite role.

Allowed File Cabinet Access is not a universal visibility filter. The list does not filter folder listings, file-name searches, path lookups, or record attachments. Administrators should review those operations separately from file-content reading and upload access.

For validation, test reading, uploading, and replacing independently under the intended user role. Also check what that role can discover through searches and path lookups. This separates the configured content-access restrictions from the role permissions that still govern files, folders, and records.

Which File Cabinet Tools Are Available?

The tools complement the interactive apps with file discovery, path resolution, and record attachment operations. Existing NetSuite file, folder, and record permissions continue to apply.

Keep three boundaries in mind when designing a workflow. File-name search should not be treated as file-content search. Detaching a file removes the record association, not the file itself. The folder-listing tool lists direct contents; do not assume recursive traversal from that description.

What Does the Runtime Session Tool Return?

The runtime session tool returns NetSuite account and role information, enabled features, granted permissions, and supported preference values for the AI client connection. This provides connection-specific context when assessing an operation's prerequisites.

As a troubleshooting practice, inspect this context when investigating a failed file operation or record transformation. Compare the returned role, features, and permissions with the operation's requirements. The documented capability is inspection, not changing connection permissions or account configuration.

How Do Record Transformations Work?

Record transformation tools let users identify supported transformations and create new records from existing records. The documented example is creating invoices from sales orders. Success depends on account configuration, role permissions, and source-record eligibility.

Before building a workflow around a transformation, verify that it is supported and test an eligible source record using the intended role. Do not treat the sales-order example as a guarantee that every sales order can become an invoice. The source does not enumerate all transformations or eligibility rules.

Who This Affects

• Administrators: Configure allowed-folder access and review its interaction with NetSuite role permissions. Validate discovery and attachment operations separately from content access.
• Integration developers: Account for complete file paths, internal IDs, attachment behavior, runtime context, and transformation prerequisites.
• AI client users: Prepare complete paths for Get File, confirm content retrieval when prompted, and review replacement confirmations before proceeding.
• Transaction-processing teams: Validate transformation support and source-record eligibility before relying on record transformations.

For related documentation planning, review the NetSuite help updates covering AI and MCP tools.

Key Takeaways

• MCP Standard Tools SuiteApp version 3.0.0 includes File Cabinet apps and tools, runtime session information, and record transformation enhancements.
• File reads, uploads, and replacements require configured allowed-folder access plus existing role permissions.
• Allowed-folder settings do not filter listings, file-name searches, path lookups, or record attachments.
• Runtime session details expose connection context; transformation success depends on configuration, permissions, and source eligibility.