Create a crypto charge — a one-time merchant invoice priced in local fiat that a buyer can settle in BTC, ETH, USDC, and other supported assets. Returns a hosted_url the buyer can be redirected to, plus per-asset payment addresses.
AI agents use create_charge 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 creates merchant invoices and facilitates cryptocurrency payments, which constitutes commitment of financial obligations and movement of money. Even though it generates a hosted URL rather than directly executing the payment, the tool's core function is to establish and enable financial transactions. The ability to create charges that result in actual cryptocurrency transfers makes this a Financial risk.
From the tool's definition Tool description states: 'Create a crypto charge — a one-time merchant invoice priced in local fiat that a buyer can settle in BTC, ETH, USDC, and other supported assets.' The explicit mention of creating invoices, pricing, and settlement in cryptocurrency…
Documented attack patterns abuse exactly the kind of access create_charge 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_charge:
{
"version": "1",
"default": "deny",
"tools": {
"create_charge": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_charge is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a crypto charge — a one-time merchant invoice priced in local fiat that a buyer can settle in BTC, ETH, USDC, and other supported assets. Returns a hosted_url the buyer can be redirected to, plus per-asset payment addresses. 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_charge: 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_charge 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_charge 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_charge. 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_charge 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.