Reconcile Razorpay payments against Odoo orders. Fetches payments and orders from Razorpay, matches them against Odoo sale orders, and classifies each as: matched, unmatched, refund, or failed. Creates draft journal entries in Odoo for matched payments. Args: from_date: Start date (YYYY-MM-DD). D...
AI agents use reconcile_orders to create or update resources in Razorpay Recon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Razorpay Recon environment.
The tool fetches and matches payment data (Read) but also creates draft journal entries in Odoo, which is a Write operation that modifies financial records. While it doesn't move money directly, creating journal entries in an accounting system is a significant financial record mutation.
From the tool's definition Creates draft journal entries in Odoo for matched payments
Attacks that exploit this kind of access
Reconcile Razorpay payments against Odoo orders. Fetches payments and orders from Razorpay, matches them against Odoo sale orders, and classifies each as: matched, unmatched, refund, or failed. Creates draft journal entries in Odoo for matched payments. Args: from_date: Start date (YYYY-MM-DD). Defaults to yesterday. to_date: End date (YYYY-MM-DD). Defaults to today. Returns: Reconciliation summary with match counts, rate, and transaction details. It is categorised as a Write tool in the Razorpay Recon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Razorpay Recon MCP server in PolicyLayer and add a rule for reconcile_orders: 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.
reconcile_orders is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reconcile_orders 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 reconcile_orders. 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.
reconcile_orders 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 →