AI agents use create_ewallet_charge to commit financial operations through Xendit — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly creates charges against e-wallet accounts (OVO, DANA, GoPay, GCash), which constitutes moving money and establishing financial obligations. Misuse by an AI agent could result in unauthorized charges, financial loss to users, and potential fraud. The tool's primary purpose is to process financial transactions, making it the most severe category.
From the tool's definition Tool name 'create_ewallet_charge' and description 'Create an e-wallet charge (OVO, DANA, GoPay, GCash)' indicate initiation of financial transactions that move money or commit financial obligations through e-wallet payment processors.
Attacks that exploit this kind of access
Create an e-wallet charge (OVO, DANA, GoPay, GCash). It is categorised as a Financial tool in the Xendit MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Xendit MCP server in PolicyLayer and add a rule for create_ewallet_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 Xendit. Nothing to install.
create_ewallet_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 create_ewallet_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 create_ewallet_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.
create_ewallet_charge is provided by the Xendit MCP server (theyahia/xendit-mcp). 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 →