Model Context Protocol moderate risk

Adls

ADLS2 MCP server provides a standardized interface for interacting with Azure Data Lake Storage Gen2, enabling file operations through MCP tools.

Connections & Capabilities

Connects To

GitHubFilesystemAzure

Capabilities

readwriteadmin

Quickstart

Install

pip install -e ".[dev]"

Config

{
    "mcpServers": {
        "adls2": {
            "command": "adls2-mcp-server",
            "env": {
                "LOG_LEVEL": "DEBUG",
                "UPLOAD_ROOT": "/path/to/store/uploads",
                "DOWNLOAD_ROOT": "/path/to/store/downloads",
                "AZURE_STORAGE_ACCOUNT_NAME": "your-azure-adls2-storage-account-name",
                "READ_ONLY_MODE": "false"
            }
        }
    }
}

Exposed MCP Tools (16)

safe

list_filesystems

Lists all filesystems in the Azure Data Lake Storage Gen2 account.

Read-only operation that does not modify any data.

moderate

create_filesystem

Creates a new filesystem (container) in the ADLS2 storage account.

Creates a new filesystem, which can impact storage organization.

critical

delete_filesystem

Deletes an existing filesystem from the ADLS2 storage account.

Deletes an entire filesystem and all its contents.

moderate

upload_file

Uploads a file to a specified path in the ADLS2 storage account.

Writes data to the storage account, potentially overwriting existing files.

safe

download_file

Downloads a file from the ADLS2 storage account to a local path.

Read-only operation that retrieves data from the storage account.

safe

file_exists

Checks if a file exists at a given path in the ADLS2 storage account.

Read-only operation that does not modify any data.

high

rename_file

Renames or moves a file within the ADLS2 storage account.

Modifies the file structure and can potentially lead to data loss if not handled carefully.

safe

get_file_properties

Retrieves properties of a file in the ADLS2 storage account.

Read-only operation that does not modify any data.

safe

get_file_metadata

Retrieves metadata associated with a file in the ADLS2 storage account.

Read-only operation that does not modify any data.

moderate

set_file_metadata

Sets metadata for a file in the ADLS2 storage account.

Modifies file metadata, which can affect data management and organization.

moderate

set_file_metadata_json

Sets multiple metadata key-value pairs for a file using JSON format.

Modifies file metadata, which can affect data management and organization.

moderate

create_directory

Creates a new directory in the ADLS2 storage account.

Creates a new directory, which can impact storage organization.

high

delete_directory

Deletes a directory from the ADLS2 storage account.

Deletes a directory and all its contents.

high

rename_directory

Renames or moves a directory within the ADLS2 storage account.

Modifies the directory structure and can potentially lead to data loss if not handled carefully.

safe

directory_exists

Checks if a directory exists at a given path in the ADLS2 storage account.

Read-only operation that does not modify any data.

safe

directory_get_paths

Gets all paths under the specified directory in the ADLS2 storage account.

Read-only operation that does not modify any data.

Safety Assessment

The ADLS2 MCP server can be safe if operated in read-only mode with properly configured Azure ADLS2 permissions. Risks arise when write operations are enabled, especially if the storage account key is exposed or permissions are overly permissive. Careful configuration and monitoring are essential.

Read-only mode can be enabled to prevent accidental data modification.
Authentication relies on Azure CLI credentials or storage account key, providing access control.
File operations are confined to the specified upload and download roots.
Uses standard Model Context Protocol for interaction.

If not configured correctly, the server can perform write and delete operations on ADLS2.
Incorrectly configured permissions on the ADLS2 storage account can lead to unauthorized access.
Exposure of the Azure Storage Account Key can lead to complete compromise of the storage account.
Lack of input validation could potentially lead to path traversal vulnerabilities.