Create a numtoken (Getnet card-on-file PAN-level token). Use for recurring or one-click-checkout flows where the merchant stores the numtoken and later hydrates it via tokenize_card to obtain a number_token at authorization time.
AI agents use create_numtoken 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 creates a payment card token (PAN-level tokenization) used for recurring billing and one-click checkout flows. Storing card-on-file tokens directly enables future financial transactions without re-entering card details, placing it firmly in the Financial category. Misuse could allow unauthorized recurring charges or fraudulent purchases, representing high blast radius.
From the tool's definition Create a numtoken (Getnet card-on-file PAN-level token). Use for recurring or one-click-checkout flows where the merchant stores the numtoken and later hydrates it via tokenize_card to obtain a number_token at authorization time.
Documented attack patterns abuse exactly the kind of access create_numtoken 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 create_numtoken:
{
"version": "1",
"default": "deny",
"tools": {
"create_numtoken": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to create_numtoken is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a numtoken (Getnet card-on-file PAN-level token). Use for recurring or one-click-checkout flows where the merchant stores the numtoken and later hydrates it via tokenize_card to obtain a number_token at authorization time. 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 create_numtoken: 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.
create_numtoken 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_numtoken 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_numtoken. 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_numtoken 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.