Confirm (accept) a buyer-initiated return request by return_sn.
AI agents use confirm_return 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 tool accepts/confirms a return request, which is a reversible write operation that modifies the state of a return transaction. It does not directly move money (though it may trigger downstream refund processes), and it doesn't irreversibly delete data. The financial implication is indirect, so Write is the most appropriate category.
From the tool's definition Confirm (accept) a buyer-initiated return request by return_sn
Documented attack patterns abuse exactly the kind of access confirm_return 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 confirm_return:
{
"version": "1",
"default": "deny",
"tools": {
"confirm_return": {
"limits": [
{
"counter": "confirm_return_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} confirm_return 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.
Confirm (accept) a buyer-initiated return request by return_sn. 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 confirm_return: 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.
confirm_return 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 confirm_return 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 confirm_return. 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.
confirm_return 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.