Low Risk

query_payment

Look up a payment by the merchant-side transactionReference you assigned on authorize_payment. Returns the matching payment event(s).

How to control query_payment ↓

What query_payment does on Mcp Afip

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

This tool performs a read-only lookup of payment information based on a reference identifier. It retrieves and returns existing payment data without creating, modifying, deleting, or executing any financial transactions. The blast radius of misuse is low — an attacker could view payment records they may not be authorized to see, but cannot move money or cause irreversible harm.

From the tool's definition Tool description explicitly states 'Look up a payment' and 'Returns the matching payment event(s)' — this is a retrieval/query operation with no side effects. The transactionReference is used as a lookup key, not to modify data.

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

How to control query_payment

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

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

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

What does the query_payment tool do? +

Look up a payment by the merchant-side transactionReference you assigned on authorize_payment. Returns the matching payment event(s). 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 query_payment? +

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

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

Can I rate-limit query_payment? +

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

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

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