Mint a Braintree client token via createClientToken for client-side tokenization (Drop-in, Hosted Fields, mobile SDKs). Pass a customerId to scope the token to a customer for vault-aware flows.
AI agents invoke create_client_token to trigger actions in Mcp Ap2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an operation on the Braintree payment gateway to generate an authentication token. While it doesn't directly move money, it creates a credential used to initiate payment flows and vault-aware operations, making it an Execute-level action with medium severity — misuse could enable unauthorized payment tokenization or vault access.
From the tool's definition Mint a Braintree client token via createClientToken for client-side tokenization
Documented attack patterns abuse exactly the kind of access create_client_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_client_token:
{
"version": "1",
"default": "deny",
"tools": {
"create_client_token": {
"limits": [
{
"counter": "create_client_token_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} create_client_token stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mint a Braintree client token via createClientToken for client-side tokenization (Drop-in, Hosted Fields, mobile SDKs). Pass a customerId to scope the token to a customer for vault-aware flows. It is categorised as a Execute tool in the Mcp Ap2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_client_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_client_token is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_client_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_client_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_client_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.