Retrieve chargeback (contestacao) detail for a charge: reason code, acquirer deadline, dispute amount, evidence status.
AI agents call query_chargeback 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 performs read-only data retrieval of chargeback dispute information. It queries existing dispute metadata without creating, modifying, deleting, or executing external operations. The blast radius of accidental misuse is minimal since it only exposes information already in the system. Confidence is high because the description clearly indicates retrieval behavior ('Retrieve...detail').
From the tool's definition Tool name contains 'query' and description states 'Retrieve chargeback detail' — it retrieves data about chargebacks (reason code, acquirer deadline, dispute amount, evidence status) with no modification or side effects.
Documented attack patterns abuse exactly the kind of access query_chargeback 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 query_chargeback:
{
"version": "1",
"default": "deny",
"tools": {
"query_chargeback": {}
}
} query_chargeback 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.
Retrieve chargeback (contestacao) detail for a charge: reason code, acquirer deadline, dispute amount, evidence status. 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 query_chargeback: 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.
query_chargeback 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 query_chargeback 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 query_chargeback. 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.
query_chargeback 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.