List Pix transactions received by the merchant during a period. Uses BACEN Pix v2 /pix collection with ISO-8601 bounds.
AI agents call list_pix_received 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 and queries historical Pix transaction records filtered by a time period. It has no side effects, does not execute code or commands, does not modify data, and does not move money. It is a straightforward read/query operation. While Pix is a Brazilian payment system (distinct from AFIP which is Argentine), the tool's function remains a data retrieval operation.
From the tool's definition Tool name 'list_pix_received' and description states 'List Pix transactions received' — a retrieval operation with no modification or execution capability. Uses BACEN Pix v2 API endpoint for querying historical transaction data.
Documented attack patterns abuse exactly the kind of access list_pix_received 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_pix_received:
{
"version": "1",
"default": "deny",
"tools": {
"list_pix_received": {}
}
} list_pix_received 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 Pix transactions received by the merchant during a period. Uses BACEN Pix v2 /pix collection with ISO-8601 bounds. 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_pix_received: 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_pix_received 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_pix_received 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_pix_received. 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_pix_received 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.