Low Risk

find_merchant_account

Fetch a merchant account by id via the GraphQL node(id:) query. Returns id, status, currencyCode, and default flag — useful for multi-currency / multi-entity merchants.

How to control find_merchant_account ↓

What find_merchant_account does on Mcp Afip

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

This tool retrieves merchant account metadata via a GraphQL query without any side effects. It does not create, modify, delete, or execute operations — it simply queries and returns account information. The blast radius of misuse is minimal (information disclosure only). Severity is low because exposure of merchant account metadata carries modest risk in the context of financial systems.

From the tool's definition Tool description states 'Fetch a merchant account by id' and 'Returns id, status, currencyCode, and default flag' — these are retrieval operations with no modification capability. The term 'Fetch' is a classic Read operation.

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

How to control find_merchant_account

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

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

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

What does the find_merchant_account tool do? +

Fetch a merchant account by id via the GraphQL node(id:) query. Returns id, status, currencyCode, and default flag — useful for multi-currency / multi-entity merchants. 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 find_merchant_account? +

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

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

Can I rate-limit find_merchant_account? +

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

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

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