Prepare an unsigned XLS-40 DIDSet transaction. This server does not sign or custody keys; sign externally and verify the signed blob before submission.
AI agents use did_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.
The tool prepares (but does not execute) a transaction to set/modify a DID on the XRP Ledger. This is a Write action because it creates or modifies data reversibly—the transaction must be signed and submitted by the user externally, and DID records can be updated or deleted later. It is not Execute because the tool itself does not sign or submit the transaction; it only prepares an unsigned blob.
From the tool's definition Tool name 'did_prepare_set' and description 'Prepare an unsigned XLS-40 DIDSet transaction' indicate creation/modification of on-chain DID data.
Attacks that exploit this kind of access
Prepare an unsigned XLS-40 DIDSet transaction. This server does not sign or custody keys; sign externally and verify the signed blob before submission. 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.
Register the Xrpl Identity MCP server in PolicyLayer and add a rule for did_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.
did_prepare_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the did_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.
Set action: deny in the PolicyLayer policy for did_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.
did_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.
did_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 →