Read an XLS-70 Credential ledger object and report whether it exists, has been accepted, and is expired relative to the validated ledger close time.
AI agents call credential_verify to retrieve information from Xrpl Identity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
credential_verify retrieves and inspects credential data from the XRP Ledger to validate its state. It performs no writes, deletions, code execution, or financial transactions. The blast radius of misuse is minimal—an agent could only retrieve information about credentials that are already public ledger objects. This is a straightforward read operation.
From the tool's definition Tool description states it 'Read[s] an XLS-70 Credential ledger object and report[s]' on its existence, acceptance status, and expiration. The verbs 'read' and 'report' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Read an XLS-70 Credential ledger object and report whether it exists, has been accepted, and is expired relative to the validated ledger close time. It is categorised as a Read tool in the Xrpl Identity MCP Server, which means it retrieves data without modifying state.
Register the Xrpl Identity MCP server in PolicyLayer and add a rule for credential_verify: 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.
credential_verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the credential_verify 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_verify. 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_verify 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.
credential_verify 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 →