// SCAN REPORT

PayRam MCP Server

35 tools. 14 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

14 can modify or destroy data

21 read-only

35 tools total

Community server · catalogue entry verified 11/06/2026

How to control PayRam MCP Server ↓

TOOL MAP

Read (21) Write / Execute (13) Destructive / Financial (1)

MOST DANGEROUS TOOLS

Critical Risk

Financial · Critical create_payment_link This tool commits financial obligations by generating payment checkout links in a cryptocurrency payment system. Execute · Medium generate_mock_webhook_event This tool generates and presumably triggers mock webhook events sent to a local endpoint, which constitutes executing an external operation (HTTP request to an endpoint). Execute · High generate_payout_recipient_flow_snippet This tool generates and likely triggers a payout flow involving recipient creation, OTP validation, and payout execution. Write · Medium generate_env_template This tool generates configuration template files (.env) that are stored artifacts.

14 of PayRam MCP Server's 35 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL PAYRAM MCP SERVER

PolicyLayer is an MCP gateway — it sits between your AI agents and PayRam MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "create_payment_link": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "generate_env_template": {
    "limits": [
      {
        "counter": "generate_env_template_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_node_sync": {
    "limits": [
      {
        "counter": "check_node_sync_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register PayRam MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PAYRAM →

Free to start. No card required.

ALL 35 PAYRAM MCP SERVER TOOLS

FINANCIAL 1 tools

Financial create_payment_link Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id.

EXECUTE 2 tools

Execute generate_mock_webhook_event Generates a snippet to send mock Payram webhook events to your local endpoint for testing. Execute generate_payout_recipient_flow_snippet Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against th

WRITE 11 tools

Write generate_env_template Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server. Write generate_payment_route_snippet Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment. Write generate_payment_sdk_snippet Generates backend code using the official Payram JS/TS SDK to create a payment. Write generate_payout_sdk_snippet Generates a backend code snippet for creating a payout using the Payram JS/TS SDK. Write generate_referral_route_snippet Generates a backend route such as /api/referrals/create for logging referral events. Write generate_referral_sdk_snippet Generates a backend route or service snippet to create a referral event using the Payram SDK. Write generate_referral_validation_snippet Generates a snippet to validate referral IDs, statuses, and eligibility. Write generate_webhook_event_router Generates a backend event router that dispatches Payram webhook events to domain handlers. Write generate_webhook_handler Generates backend code to handle Payram webhook HTTP requests. Write onboard_agent_setup Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction Write scaffold_payram_app Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a ch

READ 21 tools

Read check_node_sync Reports whether PayRam blockchain listener workers are running and whether each chain’s RPC nodes Read check_payment_readiness Diagnoses what is NOT yet set up to accept payments, per blockchain: missing deposit wallet, Read get_agent_setup_flow Returns the step-by-step setup flow for deploying PayRam as an agent. Read get_daily_volume Returns the total payment volume for a given date, with breakdowns by network and currency. Read get_payment_summary Returns payment counts: total, open, closed, and cancelled. Read get_payram_doc_by_id Returns the markdown for a Payram doc given its id, e.g. Read get_unswept_balances Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency. Read list_currencies Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Read list_payram_docs Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as Read list_platforms Lists all external platforms (projects) for the authenticated user. Read list_recipients Lists saved withdrawal recipients (payout beneficiaries). Read lookup_payment Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. Read search_payments Search and filter payments with full control over status, network, currency, dates, Read test_payram_connection Checks the /api/v1/payment endpoint on a Payram server using baseUrl and apiKey. If they are not provided, ret Read assess_payram_project Inspects dependency files, frameworks, and .env status to suggest the next integration actions. Read generate_payment_http_snippet Generates a raw HTTP sample for creating a Payram payment in the requested language. Read generate_payment_status_snippet Generates backend code to query the status of a Payram payment. Read generate_payout_status_snippet Generates backend code to query the status of a payout using the Payram SDK. Read generate_referral_status_snippet Generates code to fetch referral progress, rewards, or status. Read generate_setup_checklist Returns a step-by-step checklist of everything a merchant must configure to start using Payram. Read suggest_file_structure Suggests a recommended backend folder/file structure for integrating Payram.

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent move money through the PayRam MCP Server MCP server? +

Yes. The PayRam MCP Server server exposes 1 financial tools including create_payment_link. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through PayRam MCP Server? +

The PayRam MCP Server server has 11 write tools including generate_env_template, generate_payment_route_snippet, generate_payment_sdk_snippet. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach PayRam MCP Server.

How many tools does the PayRam MCP Server MCP server expose? +

35 tools across 3 categories: Financial, Read, Write. 21 are read-only. 14 can modify, create, or delete data.

How do I enforce a policy on PayRam MCP Server? +

Register the PayRam MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every PayRam MCP Server tool call.

Deterministic rules across all 35 PayRam MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PAYRAM →

Free to start. No card required.

35 PayRam MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

PayRam MCP Server

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL PAYRAM MCP SERVER

// ALL 35 PAYRAM MCP SERVER TOOLS

// RELATED SERVERS

// FAQ