rucio_get_did

Return attributes and status for a DID.

Server Rucio kratsg/rucio-mcp
Category Read
Risk class Low
Parameters 00 required

What rucio_get_did does on Rucio

AI agents call rucio_get_did to retrieve information from Rucio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why rucio_get_did needs a policy

The tool retrieves metadata about a DID (Data Identifier) in Rucio without creating, modifying, or deleting any data. It is a read-only query operation with minimal blast radius if misused by an AI agent; the worst outcome would be unauthorized information disclosure about dataset attributes and status.

From the tool's definition Tool name contains 'get' and description states 'Return attributes and status' — both indicate data retrieval with no modification or side effects.

Questions about rucio_get_did

What does the rucio_get_did tool do? +

Return attributes and status for a DID. It is categorised as a Read tool in the Rucio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rucio_get_did? +

Register the Rucio MCP server in PolicyLayer and add a rule for rucio_get_did: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rucio. Nothing to install.

What risk level is rucio_get_did? +

rucio_get_did is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit rucio_get_did? +

Yes. Add a rate_limit block to the rucio_get_did rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block rucio_get_did completely? +

Set action: deny in the PolicyLayer policy for rucio_get_did. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides rucio_get_did? +

rucio_get_did is provided by the Rucio MCP server (kratsg/rucio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.