set-regular-key
Assign, change, or remove a regular key pair for an account
This record as markdown: /tools/romthpt-mcp-xrpl/set-regular-key.md
What set-regular-key does on Xrpl mcp
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.
Why set-regular-key is rated Medium
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.
Attacks that exploit this kind of access
The rule that runs set-regular-key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set-regular-key, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every set-regular-key call is checked against it from then on.
Questions about set-regular-key
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.
More on Xrpl, and thousands of servers like it.
This server
Across the catalogue