Create a new charge for payment processing
AI agents use create_charge to commit financial operations through Omise MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates charges which directly move money or commit financial obligations. As a payment processing tool on a financial services MCP server, it enables monetary transactions. This is the most severe category per the classification rules, taking precedence over Execute or Write categories. Misuse by an AI agent could result in unauthorized charges, fraudulent transactions, or financial loss.
From the tool's definition Tool name 'create_charge' combined with server description stating it 'Enables comprehensive payment processing through Omise APIs including charges' and the tool description 'Create a new charge for payment processing' explicitly indicates financial…
Attacks that exploit this kind of access
Create a new charge for payment processing. It is categorised as a Financial tool in the Omise MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for 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 Omise MCP Server. Nothing to install.
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 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 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.
create_charge is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). 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 →