Rubrik Sentinel Custom MCP Tools

Alpha-ready custom MCP tool collection for Rubrik Security Cloud data in Microsoft Sentinel, optimized for teams using Claude Code.

This repository is for a Rubrik ISV developer, partner engineer, or joint customer team that wants an agent surface such as Claude Code, GitHub Copilot in VS Code, Copilot Studio, Foundry, Security Copilot, or a product-owned agent to call focused Rubrik investigation tools over Sentinel data.

The repo does not ingest or generate telemetry. It assumes the customer already has one or both official Rubrik Security Cloud Sentinel connectors sending production data into Sentinel:

Protection-status tools reduce RubrikProtectionStatus_CL to the latest row per AssetId before counting or summing. This avoids over-counting the same asset across repeated connector polls.

What this publishes

scripts/publish-mcp-tools.py calls the Sentinel Platform Services authoring API and publishes each file in mcp-tools/*.kql as a Kqs custom MCP tool under one collection, defaulting to:

Rubrik-Sentinel-MCP-Tools

Runtime endpoint:

https://sentinel.microsoft.com/mcp/custom/Rubrik-Sentinel-MCP-Tools/

Related MCP server: Azure Log Analytics MCP Server

Tools

For detailed usage, input arguments, KQL strategy, and expected output shape, see docs/tool-reference.md.

Prerequisites

1. A Microsoft Sentinel workspace with Sentinel Platform Services / data lake enabled.

2. Production Rubrik data already flowing into RubrikProtectionStatus_CL and/or the Rubrik webhook event tables.

3. Azure CLI authenticated to the tenant that owns the Sentinel workspace:

   az login
   az account set --subscription "<subscription-id-or-name>"

4. Permission to author custom MCP collections in Sentinel Platform Services.

5. Python 3.9+.

6. Claude Code installed if you want the Claude-first local workflow.

This is an alpha/private-preview style surface. The publisher and runtime both use the Sentinel Platform Services resource ID 4500ebfb-89b6-4b14-a480-7f749797bfcd. In practice:

• The tenant must have Microsoft Sentinel data lake and the required Microsoft Defender / Sentinel Platform Services licensing enabled.

• To create, update, or delete custom tools, use an identity with Security Operator, Security Administrator, or Global Administrator privileges for the Microsoft Security experience plus read access to the target Sentinel workspace.

• To list or invoke the tools, use an identity with Security Reader or Global Reader privileges plus read access to the target Sentinel workspace.

• If API publishing is unavailable in your tenant, create the same KQL as custom tools through the Microsoft Defender portal / Advanced hunting "Save as tool" flow, then use the same runtime endpoint pattern.

Quick start for Claude Code

Clone, install, publish, and generate a Claude Code MCP config:

git clone https://github.com/MitchellGulledge3/rubrik-sentinel-mcp-tools.git
cd rubrik-sentinel-mcp-tools

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

python3 scripts/publish-mcp-tools.py \
  --collection Rubrik-Sentinel-MCP-Tools \
  --workspace-id "<workspace-customer-id>"

TOKEN=$(az account get-access-token \
  --resource 4500ebfb-89b6-4b14-a480-7f749797bfcd \
  --query accessToken -o tsv)

python3 scripts/write-claude-mcp-config.py \
  --collection Rubrik-Sentinel-MCP-Tools \
  --bearer-token "$TOKEN"

This writes a gitignored .mcp.json that Claude Code can use as a project MCP configuration. The token is short-lived; rerun the token/config command when it expires.

Suggested Claude Code prompt from the repo root:

Read this repo. Use the Rubrik-Sentinel-MCP-Tools MCP server from .mcp.json.
List the available Rubrik tools, then call Rubrik_Backup_Posture_Summary for workspace <workspace-customer-id>.
After that, call Rubrik_Ransomware_Recovery_Readiness and summarize which recovery gaps matter most.

Asset-specific prompt:

Use Rubrik_Asset_Recovery_Readiness for asset prd-sql-cluster-01 in workspace <workspace-customer-id>.
Summarize whether this asset has a current recovery point, SLA drift, archival/replication lag, and secondary copy coverage.

Run locally from the terminal

1. Copy environment template:

   cp .env.example .env

2. Edit .env:

   SENTINEL_MCP_COLLECTION=Rubrik-Sentinel-MCP-Tools
   MCP_DEFAULT_ARGUMENTS={"workspaceId":"<workspace-customer-id>"}
   MCP_TOOL_ARGUMENT_TEMPLATE={}
   # Optional fallback:
   # ASSET_NAME=prd-sql-cluster-01

3. Run tools:

   python3 run_tools.py --prompt "Summarize Rubrik backup posture" --show-raw
   python3 run_tools.py --prompt "Score Rubrik ransomware recovery readiness" --show-raw
   python3 run_tools.py --prompt "Investigate Rubrik asset prd-sql-cluster-01" --show-raw

The runner calls the real custom MCP endpoint at https://sentinel.microsoft.com/mcp/custom/<collection>/ using Azure credentials.

Run locally from VS Code / GitHub Copilot

VS Code needs an MCP server registration that includes an access token for Sentinel Platform Services:

TOKEN=$(az account get-access-token \
  --resource 4500ebfb-89b6-4b14-a480-7f749797bfcd \
  --query accessToken -o tsv)

python3 scripts/write-vscode-mcp-config.py \
  --collection Rubrik-Sentinel-MCP-Tools \
  --bearer-token "$TOKEN"

This writes .vscode/mcp.json with the HTTP MCP endpoint and Authorization: Bearer <token> header. The file is gitignored because it contains a bearer token.

Configure any MCP-capable agent

Register this remote MCP endpoint in any MCP-capable agent runtime that supports authenticated HTTP MCP servers:

https://sentinel.microsoft.com/mcp/custom/Rubrik-Sentinel-MCP-Tools/

At runtime, every tool requires:

{
  "workspaceId": "<workspace-customer-id>"
}

Rubrik_Asset_Recovery_Readiness also requires:

{
  "AssetName": "prd-sql-cluster-01"
}

workspaceId is the workspace customer ID the Sentinel custom MCP runtime uses to bind the KQL execution target. The KQL text itself does not call workspace("<id>"); target selection is handled by the platform tool runtime.

Repository map

Notes for alpha users

• The tools are read-only KQL tools.

• Protection-status tools query RubrikProtectionStatus_CL.

• Webhook event tools query Rubrik_Anomaly_Data_CL, Rubrik_Ransomware_Data_CL, Rubrik_ThreatHunt_Data_CL, and Rubrik_Events_Data_CL.

• If a workspace has no Rubrik rows, the tools execute but return zero-row or zero-count output.