List payments in a date range with optional filters. Iniciador endpoint: GET /payments.
AI agents call list_payments 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.
This tool retrieves/queries payment data without modifying it. However, severity is elevated to 'medium' rather than 'low' because payment records in a tax authority context are sensitive financial data; exposure could enable reconnaissance for fraud or tax evasion. The blast radius is limited to information disclosure without direct financial harm, hence not 'Financial' category.
From the tool's definition Tool name 'list_payments' and description 'List payments in a date range with optional filters' indicates a retrieval operation. Endpoint is GET /payments, a read-only HTTP method.
Documented attack patterns abuse exactly the kind of access list_payments gives an agent:
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:
{
"version": "1",
"default": "deny",
"tools": {
"list_payments": {}
}
} list_payments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List payments in a date range with optional filters. Iniciador endpoint: GET /payments. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for list_payments: 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.
list_payments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_payments 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.
Set action: deny in the PolicyLayer policy for list_payments. 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.
list_payments 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.
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.