Charge a stored OneClick Mall card across one or more mall merchant codes. Each details entry is a separate child charge with its own commerce_code, buy_order, amount, and installments_number.
AI agents use oneclick_authorize to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly initiates financial charges against a stored payment card across multiple merchants. It moves money by executing real payment transactions, making it Financial category. The blast radius is critical because an AI agent could trigger multiple unauthorized charges across several merchant codes in a single call.
From the tool's definition 'Charge a stored OneClick Mall card across one or more mall merchant codes' and 'Each details entry is a separate child charge with its own commerce_code, buy_order, amount'
Documented attack patterns abuse exactly the kind of access oneclick_authorize gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for oneclick_authorize:
{
"version": "1",
"default": "deny",
"tools": {
"oneclick_authorize": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to oneclick_authorize is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Charge a stored OneClick Mall card across one or more mall merchant codes. Each details entry is a separate child charge with its own commerce_code, buy_order, amount, and installments_number. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for oneclick_authorize: 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 Ap2. Nothing to install.
oneclick_authorize 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 oneclick_authorize 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_authorize. 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_authorize is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.