Low Risk

get_merchants

List the merchant receiver accounts accessible with the current API key. Useful to confirm auth + discover receiver_id values.

How to control get_merchants ↓

What get_merchants does on Mcp Afip

AI agents call get_merchants 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 get_merchants needs a policy

This tool retrieves a list of merchant accounts accessible to the authenticated user. It has no side effects, does not modify data, and does not execute external operations. It is purely informational, used for authentication confirmation and data discovery. The blast radius of misuse is minimal—an attacker gains visibility into merchant accounts but cannot modify, delete, or perform financial transactions.

From the tool's definition Tool name 'get_merchants' and description 'List the merchant receiver accounts' explicitly performs a retrieval operation. The phrase 'Useful to confirm auth + discover receiver_id values' indicates it queries existing data without modification.

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

How to control get_merchants

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 get_merchants:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_merchants": {}
  }
}

get_merchants 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 get_merchants

What does the get_merchants tool do? +

List the merchant receiver accounts accessible with the current API key. Useful to confirm auth + discover receiver_id values. 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 get_merchants? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for get_merchants: 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 get_merchants? +

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

Can I rate-limit get_merchants? +

Yes. Add a rate_limit block to the get_merchants 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 get_merchants completely? +

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

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