signer_list_prepare_set · Xrpl Identity MCP: Risk & Policy

WHAT IT DOES

What signer_list_prepare_set does on Xrpl Identity

AI agents use signer_list_prepare_set to create or update resources in Xrpl Identity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xrpl Identity environment.

WHY IT NEEDS A POLICY

Why signer_list_prepare_set needs a policy

This tool prepares a transaction that modifies the account's signer list on the XRP Ledger, which controls multisignature authority. While it only prepares (does not submit) the transaction, the prepared transaction—if submitted—would alter who can authorize transactions on behalf of the account.

From the tool's definition Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

signer_list_prepare_set Rate-limited

signer_list_prepare_set stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signer_list_prepare_set": {
      "limits": [
        {
          "counter": "signer_list_prepare_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xrpl Identity, so you can run agents against it safely.

FAQ

Questions about signer_list_prepare_set

What does the signer_list_prepare_set tool do? +

Prepare an unsigned SignerListSet transaction to create, replace, or delete an XRPL multisign signer list. This server never signs or stores keys. It is categorised as a Write tool in the Xrpl Identity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on signer_list_prepare_set? +

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

What risk level is signer_list_prepare_set? +

signer_list_prepare_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit signer_list_prepare_set? +

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

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

signer_list_prepare_set is provided by the Xrpl Identity MCP server (jarod-vyent/xrpl-identity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

signer_list_prepare_set is one line of Xrpl Identity's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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