Low Risk

search_merchant_orders

Search merchant orders with filters (last 90 days). Useful for reconciliation of Checkout Pro / Bricks flows.

How to control search_merchant_orders ↓

What search_merchant_orders does on Mcp Afip

AI agents call search_merchant_orders to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_merchant_orders needs a policy

This tool retrieves and filters historical order data within a 90-day window for reconciliation purposes. It has no side effects—it only reads merchant order information. There is no capability to modify, delete, execute commands, or move money. The low severity reflects that unauthorized access would expose transaction history but cannot directly harm financial systems or data integrity.

From the tool's definition Tool name 'search_merchant_orders' and description 'Search merchant orders with filters' indicate a query/retrieval operation.

Documented attack patterns abuse exactly the kind of access search_merchant_orders gives an agent:

How to control search_merchant_orders

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for search_merchant_orders:

policy.json
{
  "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.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_merchant_orders

What does the search_merchant_orders tool do? +

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 Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_merchant_orders? +

Register the Mcp Afip 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 Afip. Nothing to install.

What risk level is search_merchant_orders? +

search_merchant_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_merchant_orders? +

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.

How do I block search_merchant_orders completely? +

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.

What MCP server provides search_merchant_orders? +

search_merchant_orders is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.