get_server_info

THE RISK

Low Risk

Why get_server_info needs a policy

This tool retrieves server metadata and status information without modifying, executing operations, or affecting ledger state. It is a straightforward read-only query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_server_info' and description 'Get information about the connected XRP Ledger server' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_server_info gives an agent:

POLICY

How to control get_server_info

PolicyLayer is an MCP gateway — it sits between your AI agents and XRPL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_info": {}
  }
}

get_server_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register XRPL MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More XRPL MCP Server tools

Financial submit_transaction Submit a signed transaction blob to the XRP Ledger. Read get_account_info Get information about an XRP Ledger account. Read get_account_lines Get the trust lines for an XRP Ledger account. Read get_account_nfts Get the NFTs owned by an XRP Ledger account. Read get_account_transactions Get the transaction history for an XRP Ledger account. Read get_book_offers Get the order book offers for a currency pair on the DEX. Read get_transaction_info Get information about a specific transaction by its hash.

All 8 XRPL MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_server_info

What does the get_server_info tool do? +

Get information about the connected XRP Ledger server. It is categorised as a Read tool in the XRPL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_info? +

Register the XRPL MCP Server MCP server in PolicyLayer and add a rule for get_server_info: 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 Server. Nothing to install.

What risk level is get_server_info? +

get_server_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_server_info? +

Yes. Add a rate_limit block to the get_server_info 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 get_server_info completely? +

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

get_server_info is provided by the XRPL MCP Server MCP server (lgcarrier/xrpl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every XRPL MCP Server tool call.

Start from XRPL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →