Run a backtest reconciliation over the past N days. Processes historical Razorpay data, reconciles against Odoo, and calculates match rates. Does NOT create Odoo entries or send alerts — purely for validation. Args: days: Number of days to backtest (default: 30). Returns: Backtest summary with av...
AI agents call run_backtest 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.
The tool explicitly states it performs no side effects: it reads and processes historical Razorpay data, reconciles against Odoo records, and computes statistics. It is purely analytical/read-only, making it a Read category tool with low severity.
From the tool's definition Does NOT create Odoo entries or send alerts — purely for validation
Attacks that exploit this kind of access
Run a backtest reconciliation over the past N days. Processes historical Razorpay data, reconciles against Odoo, and calculates match rates. Does NOT create Odoo entries or send alerts — purely for validation. Args: days: Number of days to backtest (default: 30). Returns: Backtest summary with average match rate, total anomalies, and date range. 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 run_backtest: 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.
run_backtest 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 run_backtest 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 run_backtest. 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.
run_backtest 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 →