// SCAN REPORT

Rucio

45 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

6 can modify or destroy data

39 read-only

45 tools total

Community server · catalogue entry verified 29/06/2026

How to control Rucio ↓

TOOL MAP

What Rucio exposes to your agents

Read (39) Write / Execute (5) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Rucio tools

Destructive · High rucio_delete_rule The tool name explicitly contains 'delete', which is a destructive operation that cannot be undone. Write · High rucio_add_rule Adding a rule in a distributed data management system creates or modifies data placement and replication policies, which are reversible administrative changes. Write · Medium rucio_approve_rule This tool changes the state of a replication rule by approving it, which affects data replication policies. Write · High rucio_move_rule Based on the tool name 'rucio_move_rule', this likely moves or migrates a replication rule from one RSE (Rucio Storage Element) to another.

6 of Rucio's 45 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Rucio

PolicyLayer is an MCP gateway — it sits between your AI agents and Rucio, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "rucio_delete_rule": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "rucio_add_rule": {
    "limits": [
      {
        "counter": "rucio_add_rule_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "rucio_get_account": {
    "limits": [
      {
        "counter": "rucio_get_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rucio — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON RUCIO →

Instant setup, no code required.

FULL CATALOGUE

All 45 Rucio tools

DESTRUCTIVE 1 tools

Destructive rucio_delete_rule rucio_delete_rule

WRITE 5 tools

Write rucio_add_rule rucio_add_rule Write rucio_approve_rule Approve a replication rule that is waiting for approval. Write rucio_deny_rule Deny a replication rule that is waiting for approval. Write rucio_move_rule rucio_move_rule Write rucio_update_rule rucio_update_rule

READ 39 tools

Read rucio_get_account Show detailed information about a Rucio account. Read rucio_get_dataset_locks rucio_get_dataset_locks Read rucio_get_dataset_locks_by_rse rucio_get_dataset_locks_by_rse Read rucio_get_did Return attributes and status for a DID. Read rucio_get_distance rucio_get_distance Read rucio_get_local_account_limits rucio_get_local_account_limits Read rucio_get_local_account_usage rucio_get_local_account_usage Read rucio_get_metadata Retrieve metadata key-value pairs for a DID. Read rucio_get_replication_rule rucio_get_replication_rule Read rucio_get_rse Show detailed information about a specific RSE. Read rucio_get_rse_limits Show the configured space limits for an RSE. Read rucio_get_rse_protocols List the transfer protocols supported by an RSE. Read rucio_get_rse_usage Show total, used, and free storage space for an RSE. Read rucio_list_account_rules rucio_list_account_rules Read rucio_list_accounts rucio_list_accounts Read rucio_list_container_replicas rucio_list_container_replicas Read rucio_list_content rucio_list_content Read rucio_list_dataset_replicas rucio_list_dataset_replicas Read rucio_list_did_rules rucio_list_did_rules Read rucio_list_dids rucio_list_dids Read rucio_list_files rucio_list_files Read rucio_list_parent_dids rucio_list_parent_dids Read rucio_list_replicas rucio_list_replicas Read rucio_list_replication_rules rucio_list_replication_rules Read rucio_list_requests rucio_list_requests Read rucio_list_requests_history rucio_list_requests_history Read rucio_list_rse_attributes List the attributes (key-value pairs) of a specific RSE. Read rucio_list_rses rucio_list_rses Read rucio_list_rule_history rucio_list_rule_history Read rucio_list_scopes rucio_list_scopes Read rucio_list_scopes_for_account rucio_list_scopes_for_account Read rucio_list_subscription_rules rucio_list_subscription_rules Read rucio_list_subscriptions rucio_list_subscriptions Read rucio_list_transfer_limits rucio_list_transfer_limits Read rucio_ping Ping the Rucio server and return its version. Read rucio_reduce_rule rucio_reduce_rule Read rucio_token_info rucio_token_info Read rucio_voms_proxy_info rucio_voms_proxy_info Read rucio_whoami Return information about the currently authenticated Rucio account.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Rucio

Can an AI agent delete data through the Rucio MCP server? +

Yes. The Rucio server exposes 1 destructive tools including rucio_delete_rule. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Rucio? +

The Rucio server has 5 write tools including rucio_add_rule, rucio_approve_rule, rucio_deny_rule. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Rucio.

How many tools does the Rucio MCP server expose? +

45 tools across 3 categories: Destructive, Read, Write. 39 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Rucio? +

Register the Rucio MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rucio tool call.

Deterministic rules across all 45 Rucio tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RUCIO →

Instant setup, no code required.

45 Rucio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.