Capture an authorized charge
AI agents use capture_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 directly executes financial transactions by converting an authorized charge into a completed payment. This is a financial operation that moves money and creates binding financial obligations. Financial category takes precedence over Execute due to its explicit money-movement nature.
From the tool's definition Tool name is 'capture_charge' and description states 'Capture an authorized charge'. The server is explicitly described as enabling 'payment processing through Omise APIs' and involves 'charges' and financial transactions.
Attacks that exploit this kind of access
Capture an authorized charge. 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 capture_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.
capture_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 capture_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 capture_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.
capture_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 →