Upload documentation/evidence for a chargeback dispute. Accepts one or more files as base64 content.
AI agents use upload_chargeback_evidence to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
This is a Write operation because it creates or uploads new data (evidence files) into the chargeback dispute system. While it modifies state in a financial dispute context, it is reversible (evidence can be replaced or removed) and does not directly move money or execute arbitrary code. It is not Destructive because uploads are not irreversible deletions.
From the tool's definition The tool "upload_chargeback_evidence" accepts and stores "documentation/evidence" files as "base64 content", which constitutes data creation/modification in a financial dispute context.
Documented attack patterns abuse exactly the kind of access upload_chargeback_evidence 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 upload_chargeback_evidence:
{
"version": "1",
"default": "deny",
"tools": {
"upload_chargeback_evidence": {
"limits": [
{
"counter": "upload_chargeback_evidence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_chargeback_evidence stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload documentation/evidence for a chargeback dispute. Accepts one or more files as base64 content. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for upload_chargeback_evidence: 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.
upload_chargeback_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upload_chargeback_evidence 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 upload_chargeback_evidence. 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.
upload_chargeback_evidence 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.