Tokenize a card (POST /tokens). Returns a token id like tkn_xxx. Tokenization is typically done client-side via culqi.js or mobile SDKs; this tool is primarily for test scripts and integration tests. Never send real PANs from a backend without PCI scope.
AI agents use create_token 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 handles payment card data (PANs) and creates payment tokens used in financial transactions. While tokenization itself doesn't move money, it directly enables financial operations and involves highly sensitive cardholder data. Misuse could expose PAN data or create tokens used for unauthorized payments, placing it firmly in the Financial category with high severity due to PCI/payment risk.
From the tool's definition Tokenize a card (POST /tokens). Returns a token id like tkn_xxx... Never send real PANs from a backend without PCI scope.
Documented attack patterns abuse exactly the kind of access create_token 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_token:
{
"version": "1",
"default": "deny",
"tools": {
"create_token": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_token is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Tokenize a card (POST /tokens). Returns a token id like tkn_xxx. Tokenization is typically done client-side via culqi.js or mobile SDKs; this tool is primarily for test scripts and integration tests. Never send real PANs from a backend without PCI scope. 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_token: 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_token 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_token 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_token. 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_token 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.