Accept a credential that was issued to your account. The credential must be accepted by the subject for it to be considered valid. After acceptance, the reserve burden transfers from the issuer to the subject.
AI agents use credential-accept 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.
This tool modifies ledger state by accepting a credential and triggering a reserve burden transfer between accounts. While not permanently destructive (the credential relationship could theoretically be undone through other means), it creates a binding commitment that changes account obligations.
From the tool's definition Tool name 'credential-accept' and description stating it 'Accept[s] a credential' and causes 'reserve burden transfers from the issuer to the subject', indicating irreversible state changes on the XRP Ledger.
Documented attack patterns abuse exactly the kind of access credential-accept 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 credential-accept:
{
"version": "1",
"default": "deny",
"tools": {
"credential-accept": {
"limits": [
{
"counter": "credential-accept_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}credential-accept 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.
Accept a credential that was issued to your account. The credential must be accepted by the subject for it to be considered valid. After acceptance, the reserve burden transfers from the issuer to the subject. 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 credential-accept: 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.
credential-accept 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 credential-accept 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 credential-accept. 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.
credential-accept 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.