razorpay-mcp-guard
Enforces spend-policy controls on Razorpay MCP tools, including per-agent daily, monthly, and lifetime spend caps, category allowlists, approval thresholds for large amounts, and an append-only audit ledger.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@razorpay-mcp-guardWhat's my remaining daily spend cap for payment tools?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
razorpay-mcp-guard
Spend-policy enforcement middleware for Razorpay's MCP server.
Razorpay's official MCP server executes what it's told. Nothing in the stack vets
what an agent is allowed to tell it. razorpay-mcp-guard is an MCP middleware
that sits between the LLM agent and the Razorpay MCP tools, enforcing:
Per-agent spend caps — daily / monthly / lifetime limits, enforced in paise.
Category allowlists — only whitelisted tool categories (e.g.
payments,settlements) are reachable; everything else is blocked at the gate.Approval thresholds — calls above a configurable rupee amount require explicit human approval before they reach Razorpay.
Every decision (allow, block, escalate) lands in an append-only audit ledger with hash-chained entries, so the trail itself is tamper-evident.
┌─────────────┐ tools/call ┌──────────────────┐ policy: ALLOW ┌──────────────────┐
│ LLM Agent │ ──────────────────► │ mcp-guard │ ─────────────────► │ Razorpay MCP │
│ (any client)│ ◄────────────────── │ (this proxy) │ ◄───────────────── │ server │
└─────────────┘ result └──────────────────┘ result └──────────────────┘
│ ▲
BLOCK/ESCALATE approve/deny
▼ │
Policy Engine + Audit Ledger + Approval GateStatus
Work in progress — see docs/architecture.md.
Related MCP server: dingdawg-agent-wallet
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Pre-spend firewall for AI agents. Approves, blocks, flags transactions against policy rules.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
- gatewayOAuthai.sealgate
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.
Related MCP Servers
AlicenseNot gradedqualityCmaintenancePolicy enforcement gateway for MCP tool calls, evaluating every tool invocation against declarative YAML policies (allow/deny/escalate-to-human), generating cryptographic hash-chained audit receipts, and including built-in content safety scanning.2MIT- FlicenseNot gradedqualityDmaintenanceProvides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.-
- AlicenseNot gradedqualityAmaintenanceDeterministic, auditable payment policy enforcement for AI agents. It provides pre-action authorization with scopes, budgets, allowlists, and signed mandates via an MCP server.MIT
- AlicenseNot gradedqualityBmaintenanceA policy enforcement, audit, and evaluation control plane for LLM agents on payment infrastructure, intercepting tool calls at the MCP boundary to classify, redact, and allow/deny/escalate actions before execution.MIT