Start a OneClick Mall card-enrollment flow. Returns { token, url_webpay } — redirect the user to complete enrollment. After return to response_url, call oneclick_finish_inscription.
AI agents use oneclick_create_inscription 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 initiates a card enrollment/registration flow, which creates a new record (card enrollment) in the payment system. It is a Write operation as it creates a new enrollment session. While it touches financial infrastructure, it does not itself move money or commit financial obligations — it only begins a card registration process.
From the tool's definition Start a OneClick Mall card-enrollment flow. Returns { token, url_webpay } — redirect the user to complete enrollment.
Documented attack patterns abuse exactly the kind of access oneclick_create_inscription 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 oneclick_create_inscription:
{
"version": "1",
"default": "deny",
"tools": {
"oneclick_create_inscription": {
"limits": [
{
"counter": "oneclick_create_inscription_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} oneclick_create_inscription 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.
Start a OneClick Mall card-enrollment flow. Returns { token, url_webpay } — redirect the user to complete enrollment. After return to response_url, call oneclick_finish_inscription. 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 oneclick_create_inscription: 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.
oneclick_create_inscription 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 oneclick_create_inscription 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 oneclick_create_inscription. 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.
oneclick_create_inscription 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.