Low Risk

get_payment_details

Fetch a payment object by id via GET /v2/payments/{type}/{id}. type is one of

How to control get_payment_details ↓

What get_payment_details does on Mcp Afip

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

This tool retrieves payment information without modifying, deleting, or executing any operations. Even though it accesses financial data within an AFIP (tax authority) system, the action itself is read-only. The blast radius of exposure is limited to information disclosure rather than unauthorized financial transactions or state changes.

From the tool's definition Tool name "get_payment_details" and description explicitly states "Fetch a payment object by id via GET". The GET HTTP method and "Fetch" verb indicate data retrieval with no side effects.

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

How to control get_payment_details

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

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

get_payment_details 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_payment_details

What does the get_payment_details tool do? +

Fetch a payment object by id via GET /v2/payments/{type}/{id}. type is one of. 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_payment_details? +

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

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

Can I rate-limit get_payment_details? +

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

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

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