Create a new payment chain
AI agents use create_chain to commit financial operations through Omise MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating a payment chain establishes financial infrastructure for routing or processing payments through Omise's platform. Given the server's focus on payment processing and the sibling tools (create_charge, create_schedule, create_refund), a 'chain' likely connects financial accounts or schedules recurring financial operations, placing it firmly in the Financial category with high severity due to potential for…
From the tool's definition "Create a new payment chain" on a server that handles "charges, customers, transfers, refunds, disputes, recurring payments" — payment chains link financial entities for fund routing or recurring payment flows.
Attacks that exploit this kind of access
Create a new payment chain. 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_chain: 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_chain 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_chain 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_chain. 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_chain 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 →