Low Risk

list_payments_by_date

List payments created within a date range. Supports cursor pagination via limit + offset. Useful for reconciliation and reporting.

How to control list_payments_by_date ↓

What list_payments_by_date does on Mcp Afip

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

This tool retrieves historical payment records for analysis without creating, modifying, or deleting data. The mention of cursor pagination (limit + offset) is typical of read-only list operations. Accessing payment history is a standard auditing/reporting function with no destructive or executable capabilities.

From the tool's definition Tool name 'list_payments_by_date' and description 'List payments created within a date range' indicate data retrieval only. The phrase 'Useful for reconciliation and reporting' confirms a query/reporting purpose with no side effects.

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

How to control list_payments_by_date

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

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

list_payments_by_date 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_payments_by_date

What does the list_payments_by_date tool do? +

List payments created within a date range. Supports cursor pagination via limit + offset. Useful for reconciliation and reporting. 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_payments_by_date? +

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

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

Can I rate-limit list_payments_by_date? +

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

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

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