Create an AP2 cart mandate — a signed, locked-cart commitment from a merchant binding line items, totals, and merchant attestation.
AI agents use create_cart_mandate 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.
The tool creates a binding mandate document that commits a merchant to specific financial terms and amounts. While not executing a payment itself, it creates an enforceable financial obligation document ('signed, locked-cart commitment'). This is Write rather than Financial because the mandate creation is the primary action, though it has Financial implications.
From the tool's definition Creates a signed, locked-cart commitment that binds merchant attestations, line items, and totals—this irreversibly locks financial commitment terms for a transaction with an Argentine tax authority (AFIP).
Documented attack patterns abuse exactly the kind of access create_cart_mandate 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_cart_mandate:
{
"version": "1",
"default": "deny",
"tools": {
"create_cart_mandate": {
"limits": [
{
"counter": "create_cart_mandate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_cart_mandate 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.
Create an AP2 cart mandate — a signed, locked-cart commitment from a merchant binding line items, totals, and merchant attestation. 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 create_cart_mandate: 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_cart_mandate 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 create_cart_mandate 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_cart_mandate. 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_cart_mandate 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.