run_daily_reconciliation · Razorpay Recon MCP: Risk & Policy

WHAT IT DOES

What run_daily_reconciliation does on Razorpay Recon

AI agents invoke run_daily_reconciliation to trigger actions in Razorpay Recon. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_daily_reconciliation needs a policy

This tool triggers a multi-step external pipeline: fetching payment data, reconciling records, creating journal entries in Odoo (Write), and sending WhatsApp notifications (external communication). It spans Write and Execute categories, and while it touches financial data, it does not itself move money or commit financial obligations — it creates draft journal entries.

From the tool's definition 'Run the full daily reconciliation pipeline', 'creates Odoo draft journal entries', 'sends WhatsApp summary to finance team'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_daily_reconciliation Rate-limited

run_daily_reconciliation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_daily_reconciliation": {
      "limits": [
        {
          "counter": "run_daily_reconciliation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Razorpay Recon, so you can run agents against it safely.

FAQ

Questions about run_daily_reconciliation

What does the run_daily_reconciliation tool do? +

Run the full daily reconciliation pipeline. Fetches all Razorpay data for the previous day, reconciles against Odoo orders, detects anomalies (large failures >₹5K, unmatched settlements, refund spikes), creates Odoo draft journal entries, and sends WhatsApp summary to finance team. Returns: Full pipeline result with payment counts, match rates, anomalies, and Odoo entries created. It is categorised as a Execute tool in the Razorpay Recon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_daily_reconciliation? +

Register the Razorpay Recon MCP server in PolicyLayer and add a rule for run_daily_reconciliation: 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.

What risk level is run_daily_reconciliation? +

run_daily_reconciliation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_daily_reconciliation? +

Yes. Add a rate_limit block to the run_daily_reconciliation 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.

How do I block run_daily_reconciliation completely? +

Set action: deny in the PolicyLayer policy for run_daily_reconciliation. 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.

What MCP server provides run_daily_reconciliation? +

run_daily_reconciliation 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.