Assign, change, or remove a regular key pair for an account
AI agents use set-regular-key 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.
set-regular-key modifies account configuration by changing signing keys, which is a reversible write operation. While it could enable unauthorized access if misused, the operation itself is Write (not Execute, as it doesn't trigger arbitrary code execution).
From the tool's definition Tool description states 'Assign, change, or remove a regular key pair for an account' — this modifies account security settings reversibly.
Documented attack patterns abuse exactly the kind of access set-regular-key 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 set-regular-key:
{
"version": "1",
"default": "deny",
"tools": {
"set-regular-key": {
"limits": [
{
"counter": "set-regular-key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set-regular-key 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.
Assign, change, or remove a regular key pair for an account. 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 set-regular-key: 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.
set-regular-key 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 set-regular-key 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 set-regular-key. 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.
set-regular-key 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.