Search merchant orders with filters (last 90 days). Useful for reconciliation of Checkout Pro / Bricks flows.
AI agents call search_merchant_orders to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches existing merchant order records filtered by time period (last 90 days). It performs no data modification, deletion, or external operation triggering. While it accesses financial transaction data within a payment protocol server, the tool itself only reads/queries that data for reconciliation purposes, placing it squarely in the Read category at low severity.
From the tool's definition Tool name 'search_merchant_orders' and description 'Search merchant orders with filters' indicate a query operation. The phrase 'Useful for reconciliation' suggests read-only analysis of historical payment data without modification capability.
Documented attack patterns abuse exactly the kind of access search_merchant_orders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for search_merchant_orders:
{
"version": "1",
"default": "deny",
"tools": {
"search_merchant_orders": {}
}
}search_merchant_orders is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search merchant orders with filters (last 90 days). Useful for reconciliation of Checkout Pro / Bricks flows. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for search_merchant_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 Mcp Ap2. Nothing to install.
search_merchant_orders 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 search_merchant_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 search_merchant_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.
search_merchant_orders is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.