Low Risk

list_payment_intents

List payment intents with optional filters (status, merchant_order_id, date range). Supports pagination via page_num / page_size.

How to control list_payment_intents ↓

What list_payment_intents does on Mcp Afip

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

This tool performs a read-only retrieval operation on existing payment intent data. It does not create, modify, delete, or execute any operations. The filters and pagination are standard query parameters that refine the retrieval scope.

From the tool's definition Tool name and description: 'List payment intents' — retrieves or queries payment intent records with optional filters (status, merchant_order_id, date range) and pagination support. No modification, deletion, or execution of commands.

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

How to control list_payment_intents

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

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

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

What does the list_payment_intents tool do? +

List payment intents with optional filters (status, merchant_order_id, date range). Supports pagination via page_num / page_size. 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 list_payment_intents? +

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

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

Can I rate-limit list_payment_intents? +

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

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

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