// SCAN REPORT

Omise MCP Server

69 tools. 31 can modify or destroy data without limits.

17 destructive tools with no built-in limits. Policy required.

Last updated:

31 can modify or destroy data
38 read-only
69 tools total

Community server · catalogue entry verified 29/06/2026

How to control Omise MCP Server ↓

TOOL MAP

What Omise MCP Server exposes to your agents

Read (38) Write / Execute (14) Destructive / Financial (17)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS
Critical Risk

The most dangerous Omise MCP Server tools

Financial · High capture_charge This tool directly executes financial transactions by converting an authorized charge into a completed payment. Financial · Critical create_charge This tool creates charges which directly move money or commit financial obligations. Financial · High create_refund Refunds move money from the merchant's account back to the customer, constituting a direct financial transaction. Financial · Critical create_transfer This tool commits a financial obligation by transferring money to a recipient, which is irreversible and directly impacts accounts.

31 of Omise MCP Server's 69 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Omise MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Omise MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "accept_dispute": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
{
  "destroy_customer": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "create_customer": {
    "limits": [
      {
        "counter": "create_customer_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_test_results": {
    "limits": [
      {
        "counter": "get_test_results_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Omise MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON OMISE →

Instant setup, no code required.

FULL CATALOGUE

All 69 Omise MCP Server tools

FINANCIAL 10 tools
Financial accept_dispute Accept a dispute (accept the chargeback) Financial capture_charge Capture an authorized charge Financial create_chain Create a new payment chain Financial create_charge Create a new charge for payment processing Financial create_link Create a new payment link Financial create_refund Create a refund for a charge Financial create_schedule Create a new payment schedule Financial create_transfer Create a new transfer to a recipient Financial expire_charge Expire a pending charge Financial reverse_charge Reverse an authorized charge
DESTRUCTIVE 7 tools
Destructive destroy_customer Delete a customer Destructive destroy_customer_card Delete a customer card Destructive destroy_dispute_document Delete a dispute document Destructive destroy_recipient Delete a recipient Destructive destroy_schedule Delete a schedule Destructive destroy_transfer Delete a transfer (only for pending transfers) Destructive webhook_endpoint_destroy Delete a webhook endpoint
EXECUTE 1 tools
Execute run_test_suite Run comprehensive test suite
WRITE 13 tools
Write create_customer Create a new customer Write create_recipient Create a new recipient for transfers Write create_source Create a payment source for various payment methods Write create_token Create a card token for secure payment processing Write update_charge Update charge information (only for pending charges) Write update_customer Update customer information Write update_customer_card Update a customer card Write update_dispute Update dispute information Write update_recipient Update recipient information Write update_transfer Update transfer information (only for pending transfers) Write upload_dispute_document Upload a document for a dispute Write webhook_endpoint_create Create a new webhook endpoint Write webhook_endpoint_update Update webhook endpoint information
READ 38 tools
Read get_test_results Get test results and metrics Read list_chain_revisions List chain execution history and revisions Read list_chains List all chains with optional filtering Read list_charges List all charges with optional filtering Read list_customer_cards List all cards for a customer Read list_customers List all customers with filtering options Read list_dispute_documents List all documents for a dispute Read list_disputes List all disputes with optional filtering Read list_events List all events with optional filtering Read list_links List all payment links with optional filtering Read list_recipients List all recipients with optional filtering Read list_refunds List all refunds with optional filtering Read list_schedule_occurrences List all occurrences (execution history) for a schedule Read list_schedules List all schedules with optional filtering Read list_transfers List all transfers with optional filtering Read retrieve_capability Retrieve Omise API capabilities and supported features Read retrieve_chain Retrieve chain information by ID Read retrieve_charge Retrieve charge information by ID Read retrieve_customer Retrieve customer information by ID Read retrieve_customer_card Retrieve a specific card for a customer Read retrieve_dispute Retrieve dispute information by ID Read retrieve_dispute_document Retrieve a specific dispute document Read retrieve_event Retrieve event information by ID Read retrieve_link Retrieve payment link information by ID Read retrieve_recipient Retrieve recipient information by ID Read retrieve_refund Retrieve refund information by ID Read retrieve_schedule Retrieve schedule information by ID Read retrieve_source Retrieve source information by ID Read retrieve_token Retrieve token information by ID Read retrieve_transfer Retrieve transfer information by ID Read test_a2a_authentication Test A2A agent authentication Read test_a2a_communication Test A2A secure communication Read test_a2a_registration Test A2A agent registration Read test_omise_customer Test Omise customer operations Read test_omise_payment Test Omise payment processing Read verify_recipient Verify recipient information and bank account Read webhook_endpoint_list List all webhook endpoints Read webhook_endpoint_retrieve Retrieve webhook endpoint information by ID
EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Yaver 1060 tools
paymentsadminautomation
Binance MCP Server 734 tools
paymentsadminautomation
GoHighLevel MCP Server 566 tools
paymentsadminautomation
GoCreative Agent API 546 tools
paymentsadminautomation
Claude Flow 454 tools
paymentsadminautomation
ServiceTitan MCP Server 454 tools
paymentsadminautomation
CloudStack MCP Server 442 tools
paymentsadminautomation
Integrations MCP 420 tools
paymentsadminautomation
FAQ

Questions about Omise MCP Server

Can an AI agent move money through the Omise MCP Server MCP server? +

Yes. The Omise MCP Server server exposes 10 financial tools including accept_dispute, capture_charge, create_chain. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Omise MCP Server MCP server? +

Yes. The Omise MCP Server server exposes 7 destructive tools including destroy_customer, destroy_customer_card, destroy_dispute_document. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Omise MCP Server? +

The Omise MCP Server server has 13 write tools including create_customer, create_recipient, create_source. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Omise MCP Server.

How many tools does the Omise MCP Server MCP server expose? +

69 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 38 are read-only. 31 can modify, create, or delete data.

How do I enforce a policy on Omise MCP Server? +

Register the Omise MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Omise MCP Server tool call.

Deterministic rules across all 69 Omise MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON OMISE →

Instant setup, no code required.

69 Omise MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.