Checking Backend...
Swagger REST Specs
Stage 4: JSON-RPC 2.0 Model Context Protocol GatewaySANDBOX / TEST MODE · Razorpay Test Mode

Razorpay MCP Security Gateway & Agentic Commerce

Connects AI agents to Razorpay APIs via the Model Context Protocol (MCP). Mandate acts as a security proxy that dynamically filters tool surfaces based on active financial mandates, enforces strict schema validation, isolates merchant credentials, and routes mutating tools through the Policy Engine.

Total MCP Tool Catalog

25 Tools

8 Functional Domains (Razorpay & RazorpayX)
Shopping Agent Filter

88% Reduction

3 / 25 Tools Exposed (Orders & Links)
Procurement Sub-Agent

92% Reduction

2 / 25 Tools Exposed (Orders only)
Customer Support Agent

88% Reduction

3 / 25 Tools Exposed (Refunds & Inquiries)

Direct Unprotected Razorpay MCP

UNCONSTRAINED RISK

Standard MCP architectures provide the AI agent with raw credentials and expose all 25 tool definitions in the system prompt.

Credential & Surface Exposure:Agent holds full merchant keys; prompt injection can invoke privileged payouts_create or unlimited refunds.
0 Budget Controls & Race Conditions:No per-operation caps or two-phase budget reservation. Concurrent agents can drain merchant balances.

Mandate-Protected MCP Security Gateway

BOUNDED AGENTIC COMMERCE

AI agents connect strictly to Mandate's JSON-RPC 2.0 proxy. Mandate holds credentials safely, dynamically slashes tool surfaces, and evaluates the Policy Engine synchronously.

Dynamic Tool Filtering & Schema Validation:Slashes 88%–92% of attack surface. Rejects unexpected parameter injections with strict JSON-RPC error codes.
Zero-Gateway-Dispatch Guarantee:Two-phase atomic CAS reservation commits spend only upon successful policy approval and Razorpay sandbox execution.

Interactive JSON-RPC 2.0 MCP Gateway Console

Send raw MCP protocol requests (initialize, tools/list, tools/call) and inspect live protocol responses.

Razorpay MCP JSON-RPC 2.0 Gateway