Fetch Razorpay payout details for a date range. Retrieves payout information including amount, status, UTR, and mode. Use this to check payout statuses, verify bank transfers, or reconcile payout amounts. Args: from_date: Start date (YYYY-MM-DD). Defaults to yesterday. to_date: End date (YYYY-MM-...
AI agents call get_payout_status to retrieve information from Razorpay Recon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries historical payout information for reconciliation and verification purposes. It has no side effects, does not modify any data, and does not execute external operations or commit financial transactions. While it relates to financial data, it merely retrieves existing information rather than moving money or creating financial obligations.
From the tool's definition Tool description explicitly states "Fetch Razorpay payout details" and "Retrieves payout information". The tool only queries and returns payout data (id, amount, status, utr, mode) within a date range with no modification capabilities.
Attacks that exploit this kind of access
Fetch Razorpay payout details for a date range. Retrieves payout information including amount, status, UTR, and mode. Use this to check payout statuses, verify bank transfers, or reconcile payout amounts. Args: from_date: Start date (YYYY-MM-DD). Defaults to yesterday. to_date: End date (YYYY-MM-DD). Defaults to today. Returns: List of payouts with id, amount, status, utr, and mode. It is categorised as a Read tool in the Razorpay Recon MCP Server, which means it retrieves data without modifying state.
Register the Razorpay Recon MCP server in PolicyLayer and add a rule for get_payout_status: 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 Razorpay Recon. Nothing to install.
get_payout_status 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 get_payout_status 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 get_payout_status. 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.
get_payout_status is provided by the Razorpay Recon MCP server (qalalabs/razorpay-recon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →