Create a batch payout via POST /v1/payments/payouts. sender_batch_header carries metadata; items is an array of payout_item objects each with recipient_type, amount { currency, value }, receiver, and note. Async — poll get_payout to track status.
AI agents use create_batch_payout to commit financial operations through Mcp Afip — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves money by creating batch payouts to multiple receivers. It is a Financial action with critical severity because misuse could result in large-scale unauthorized financial transfers that are difficult or impossible to reverse.
From the tool's definition 'Create a batch payout via POST /v1/payments/payouts' — initiates real monetary payouts to multiple recipients with amount, currency, and value fields
Documented attack patterns abuse exactly the kind of access create_batch_payout 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 create_batch_payout:
{
"version": "1",
"default": "deny",
"tools": {
"create_batch_payout": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_batch_payout is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a batch payout via POST /v1/payments/payouts. sender_batch_header carries metadata; items is an array of payout_item objects each with recipient_type, amount { currency, value }, receiver, and note. Async — poll get_payout to track status. It is categorised as a Financial tool in the Mcp Afip MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for create_batch_payout: 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.
create_batch_payout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_batch_payout 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 create_batch_payout. 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.
create_batch_payout 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.