Set or update Oracle data on the XRP Ledger (Requires Price Oracle amendment)
AI agents use oracle-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 modifies oracle data on the XRP Ledger, which is a reversible write operation. While it doesn't delete data (which would be Destructive) or move funds (Financial), it does alter state that other applications may depend on. Oracle data affects price feeds used by other contracts and applications, so misuse could cause significant downstream harm through corrupted price information.
From the tool's definition Set or update Oracle data on the XRP Ledger — the verb 'set or update' indicates modification of ledger state. This is a write operation that creates or modifies data on a blockchain.
Documented attack patterns abuse exactly the kind of access oracle-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 oracle-set:
{
"version": "1",
"default": "deny",
"tools": {
"oracle-set": {
"limits": [
{
"counter": "oracle-set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} oracle-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.
Set or update Oracle data on the XRP Ledger (Requires Price Oracle amendment). 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 oracle-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.
oracle-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 oracle-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 oracle-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.
oracle-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.