credential_prepare_accept · Xrpl Identity MCP: Risk & Policy

WHAT IT DOES

What credential_prepare_accept does on Xrpl Identity

AI agents use credential_prepare_accept to create or update resources in Xrpl Identity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xrpl Identity environment.

WHY IT NEEDS A POLICY

Why credential_prepare_accept needs a policy

This tool prepares a CredentialAccept transaction on the XRP Ledger, which creates/modifies on-chain credential state. It is a write operation (accepting a credential updates ledger state) but is not destructive, financial, or executing arbitrary code.

From the tool's definition Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

credential_prepare_accept Rate-limited

credential_prepare_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "credential_prepare_accept": {
      "limits": [
        {
          "counter": "credential_prepare_accept_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xrpl Identity, so you can run agents against it safely.

FAQ

Questions about credential_prepare_accept

What does the credential_prepare_accept tool do? +

Prepare an unsigned XLS-70 CredentialAccept transaction for a subject to accept an issued credential. Signing happens outside this server. It is categorised as a Write tool in the Xrpl Identity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on credential_prepare_accept? +

Register the Xrpl Identity MCP server in PolicyLayer and add a rule for credential_prepare_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 Identity. Nothing to install.

What risk level is credential_prepare_accept? +

credential_prepare_accept is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit credential_prepare_accept? +

Yes. Add a rate_limit block to the credential_prepare_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.

How do I block credential_prepare_accept completely? +

Set action: deny in the PolicyLayer policy for credential_prepare_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.

What MCP server provides credential_prepare_accept? +

credential_prepare_accept is provided by the Xrpl Identity MCP server (jarod-vyent/xrpl-identity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

credential_prepare_accept is one line of Xrpl Identity's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →