Connectors · Identity & security

Rubrik Security Cloud MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Rubrik Security Cloud and the rest of your systems. It gives your agent 2,177 Rubrik Security Cloud actions (1,191 reads, 766 writes and 220 that wait for a confirmation) and holds the Rubrik Security Cloud credential itself, so the agent never does. It paces Rubrik Security Cloud's limits and records every call.

Connect Rubrik Security Cloud free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

the first call

do {  action: "rubrik_security_cloud.users_in_current_and_descendant_organization.list",  intent: "check which Rubrik Security Cloud account is connected"}# List Rubrik users in current and descendant organizations · read · 1 upstream call

2,177actionsin one signed file
1,191readlook, never change
766writecreate and update
220wait for a yesdestructive, confirmed first

Set up

Connect Rubrik Security Cloud in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Rubrik Security Cloud.
OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.
- client_idRSC service account client ID (e.g. client|c9bba9a9-…)
- client_secretThe service account's client secret, shown once when the account is created
- hostWhere your Rubrik Security Cloud lives: your host
```
account { op: "connections.requirements", service: "rubrik_security_cloud" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "rubrik_security_cloud.users_in_current_and_descendant_organization.list" }# list rubrik users in current and descendant organizations · read · 1 upstream callcheck { action: "rubrik_security_cloud.vlan.add", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Rubrik Security Cloud at a glance

Sign-in: OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.
You provide: client_idclient_secret
Setup fields: host
Limits we pace to: 300 calls a minute, per connection
API covered: Rubrik Security Cloud API graphql v20261012-34, at your Rubrik Security Cloud instance's API base URL, which you enter when connecting
Built from: Rubrik Security Cloud's documentation, read 23 October 2026developer.rubrik.com developer.rubrik.com OpenAPI spec (GitHub)
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 1,136 of 1,191 reads, for up to an hour; a write clears what it affects
Shared entities: 5, so ask can line Rubrik Security Cloud up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Rubrik Security Cloud.

2,177 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

1,191readlook, never change
766writecreate and update
220destructivewait for a confirmation

Security
2,177
1,191 read · 766 write · 220 destructive
List Rubrik users in current and descendant organizations · List Rubrik groups in current and descendant organizations · List Rubrik all roles in orgs · Get Rubrik current user

Top actions

The Rubrik Security Cloud API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of Rubrik Security Cloud's 5 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`rubrik_security_cloud.users_in_current_and_descendant_organization.list`List Rubrik users in current and descendant organizations	Retrieve users from current and descendant organizations based on the specified filters.	read	`identity.user.list`474 connectors
`rubrik_security_cloud.groups_in_current_and_descendant_organization.list`List Rubrik groups in current and descendant organizations	Retrieve groups from current and descendant organizations based on the specified filters.	read	`identity.group.list`262 connectors
`rubrik_security_cloud.all_roles_in_org.list`List Rubrik all roles in orgs	Get all roles in the current organization with filtering, sorting, and pagination support.	read	`identity.role.list`184 connectors
`rubrik_security_cloud.current_user.get`Get Rubrik current user	Currently logged-in user.	read	`identity.current_user.get`307 connectors
`rubrik_security_cloud.service_account.list`List Rubrik service accounts	Browse service accounts.	read	`identity.service_account.list`35 connectors
`rubrik_security_cloud.org.list`List Rubrik orgs	All orgs.	read	this connector
`rubrik_security_cloud.vlan.add`Rubrik vlan: add	Add VLAN to Rubrik cluster.	write	this connector
`rubrik_security_cloud.crawl.list`List Rubrik crawls	Returns crawls for an account.	read	this connector
`rubrik_security_cloud.disk.mount`Rubrik disk: mount	Mount disks to the given workload.	write	this connector
`rubrik_security_cloud.org.create`Rubrik org: create	Create a new organization under global org.	write	this connector
`rubrik_security_cloud.vrm.create`Rubrik vrm: create	Add a FusionCompute VRM instance Supported in v9.6+ Create a FusionCompute VRM instance by providing the hostname and account credentials of the FusionCompute…	write	this connector
`rubrik_security_cloud.csr.delete`Rubrik csr: delete	Delete Certificate Signing Request.	destructive	this connector

Try it

Prompts to paste into Claude.

Each one names the Rubrik Security Cloud actions it will call, so you know what it reads and what it changes before you send it.

Readread
Who has access in Rubrik Security Cloud? List every user and their role.
callsrubrik_security_cloud.users_in_current_and_descendant_organization.list
Writewrite
Rubrik vlan: add in Rubrik Security Cloud. Show me exactly what you will send before you save it.
callsrubrik_security_cloud.vlan.add

Governance for Rubrik Security Cloud

Destructive actions wait for a yes.

220 Rubrik Security Cloud actions are destructive. The first 10:

Rubrik csr: deleterubrik_security_cloud.csr.delete
Rubrik org: deleterubrik_security_cloud.org.delete
Rubrik disk: removerubrik_security_cloud.disk.remove
Rubrik role: deleterubrik_security_cloud.role.delete
Rubrik role: mutaterubrik_security_cloud.role.mutate
Rubrik disk: unmountrubrik_security_cloud.disk.unmount
Rubrik vlans: removerubrik_security_cloud.vlans.remove
Rubrik target: deleterubrik_security_cloud.target.delete
Rubrik target: disablerubrik_security_cloud.target.disable
Rubrik webhook: deleterubrik_security_cloud.webhook.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dorubrik_security_cloud.csr.deleteconfirm_policy: human

Rubrik csr: delete?

intent: the user asked me to rubrik csr: delete

run suspended · waiting for a named person · key rubrik-security-cloud-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "rubrik-security-cloud-agent",  allowed_actions: ["rubrik_security_cloud.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "rubrik_security_cloud.csr.delete", approver: "[email protected]" },    { match: "rubrik_security_cloud.org.delete", approver: "[email protected]" },    { match: "rubrik_security_cloud.disk.remove", approver: "[email protected]" }  ]}

Illustrative. Scoped to Rubrik Security Cloud only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Rubrik Security Cloud costs on actionlake.

Every Rubrik Security Cloud action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Rubrik Security Cloud refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 2,177 Rubrik Security Cloud actions
340actions pageeach page of a long list is one call
1,136reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Rubrik Security Cloud action.

2,177 actions by area: the id your agent calls, what it does, and its effect.

Security2,177

rubrik_security_cloud.all_roles_in_org.listList Rubrik all roles in orgsread
rubrik_security_cloud.current_user.getGet Rubrik current userread
rubrik_security_cloud.groups_in_current_and_descendant_organization.listList Rubrik groups in current and descendant organizationsread
rubrik_security_cloud.users_in_current_and_descendant_organization.listList Rubrik users in current and descendant organizationsread
rubrik_security_cloud.access_granting_identity.listList Rubrik access granting identitysread
rubrik_security_cloud.access_to_o365_objects.hasRubrik access to o365 objects: hasread
and 2,171 more in this area

This index shows a sample of each area. All 2,177 actions, with their inputs and prices, are in the catalogue, which a free sandbox key can search.

Questions

The Rubrik Security Cloud MCP server, answered.

Is there a Rubrik Security Cloud MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 2,177 Rubrik Security Cloud actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Rubrik Security Cloud.

What do I need to connect Rubrik Security Cloud?

RSC service account client ID (e.g. client|c9bba9a9-…) and The service account's client secret, shown once when the account is created. Plus your host. The free call account { op: "connections.requirements", service: "rubrik_security_cloud" } lists exactly what to paste.

Can an AI agent delete or change things in Rubrik Security Cloud?

Only if its key allows it, and only with an explicit confirmation. 220 Rubrik Security Cloud actions are destructive, including rubrik csr: delete, rubrik org: delete and rubrik disk: remove. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Rubrik Security Cloud API limit?

actionlake paces every call to the limits in the Rubrik Security Cloud service file: 300 calls a minute per connection. Repeated reads are answered from cache (1,136 Rubrik Security Cloud actions can be), which never reaches Rubrik Security Cloud.

What does a Rubrik Security Cloud action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (340 Rubrik Security Cloud actions page). Cache hits, searches, dry runs and calls Rubrik Security Cloud refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Rubrik Security Cloud API does it cover?

The Rubrik Security Cloud API graphql v20261012-34 at your Rubrik Security Cloud instance's API base URL, which you enter when connecting. It is built from Rubrik Security Cloud's documentation as read on 23 October 2026. 2,177 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Rubrik Security Cloud data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Rubrik Security Cloud credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Rubrik Security Cloud today.