Low Risk

delegate-list-permissions

List all available permission names that can be delegated.

How to control delegate-list-permissions ↓

What delegate-list-permissions does on Xrpl mcp

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

Low Risk

Why delegate-list-permissions needs a policy

This tool queries and returns a static list of permission names available for delegation. It performs no creation, modification, deletion, or execution of operations. It is purely informational retrieval, fitting the Read category. The low severity reflects minimal blast radius - listing permission names cannot cause direct harm even if misused by an AI agent.

From the tool's definition Tool name includes 'list' and description states 'List all available permission names' - a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access delegate-list-permissions gives an agent:

How to control delegate-list-permissions

PolicyLayer is an MCP gateway — it sits between your AI agents and Xrpl mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for delegate-list-permissions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "delegate-list-permissions": {}
  }
}

delegate-list-permissions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Xrpl mcp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delegate-list-permissions

What does the delegate-list-permissions tool do? +

List all available permission names that can be delegated. It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on delegate-list-permissions? +

Register the Xrpl MCP server in PolicyLayer and add a rule for delegate-list-permissions: 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 Xrpl mcp. Nothing to install.

What risk level is delegate-list-permissions? +

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

Can I rate-limit delegate-list-permissions? +

Yes. Add a rate_limit block to the delegate-list-permissions 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 delegate-list-permissions completely? +

Set action: deny in the PolicyLayer policy for delegate-list-permissions. 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 delegate-list-permissions? +

delegate-list-permissions is provided by the Xrpl MCP server (romthpt/mcp-xrpl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xrpl mcp tool call.

Start from Xrpl mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

71 Xrpl mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.