Create or modify a Permissioned Domain on the XRP Ledger. Permissioned Domains define access rules based on credentials, allowing only authorized accounts (those with accepted credentials from specified issuers) to participate in certain activities.
AI agents use permissioned-domain-set to create or update resources in Xrpl mcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xrpl mcp environment.
The tool creates or modifies access control configurations (Permissioned Domains) on the XRP Ledger. While Write is the appropriate category (reversible modification of ledger state), severity is elevated to 'high' because misconfiguration or unauthorized domain creation/modification could restrict legitimate account access, lock users out of activities, or grant unintended permissions to malicious issuers, creating…
From the tool's definition Tool description states 'Create or modify a Permissioned Domain on the XRP Ledger' - 'create or modify' indicates reversible data creation/modification operations on blockchain state.
Documented attack patterns abuse exactly the kind of access permissioned-domain-set gives an agent:
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 permissioned-domain-set:
{
"version": "1",
"default": "deny",
"tools": {
"permissioned-domain-set": {
"limits": [
{
"counter": "permissioned-domain-set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}permissioned-domain-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.
Free to start. No card required.
Create or modify a Permissioned Domain on the XRP Ledger. Permissioned Domains define access rules based on credentials, allowing only authorized accounts (those with accepted credentials from specified issuers) to participate in certain activities. It is categorised as a Write tool in the Xrpl mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xrpl MCP server in PolicyLayer and add a rule for permissioned-domain-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 mcp. Nothing to install.
permissioned-domain-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 permissioned-domain-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 permissioned-domain-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.
permissioned-domain-set 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.
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.