AI agents use coinbase_create_charge to commit financial operations through VibeServe — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves money or commits financial obligations by creating a charge in Coinbase Commerce, which is a payment processor. Misuse by an AI agent could result in unauthorized charges, financial loss, or fraudulent transactions. This is a clear Financial category risk with critical severity due to the irreversible nature of payment charges and potential for significant monetary harm.
From the tool's definition Tool is named 'coinbase_create_charge' with description 'Create a Coinbase Commerce charge'. Creating a charge directly initiates a financial transaction that commits a payment obligation.
Attacks that exploit this kind of access
Create a Coinbase Commerce charge. It is categorised as a Financial tool in the VibeServe MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the VibeServe MCP server in PolicyLayer and add a rule for coinbase_create_charge: 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 VibeServe. Nothing to install.
coinbase_create_charge 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 coinbase_create_charge 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 coinbase_create_charge. 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.
coinbase_create_charge is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →