Create a new customer
AI agents use create_customer to create or update resources in Omise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omise MCP Server environment.
This tool creates new customer records in the Omise payment processing system. This is a Write operation (creates data reversibly). Severity is high because: (1) customer creation in a payment system typically involves storing sensitive personal/financial information; (2) it establishes persistent relationships in the payment platform that affect future transactions; (3) misuse could result in unauthorized customer…
From the tool's definition Tool name: 'create_customer'; description: 'Create a new customer'; server context indicates payment processing and 51 tools covering 'all Omise API functionality' including 'customers' management.
Attacks that exploit this kind of access
Create a new customer. It is categorised as a Write tool in the Omise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for create_customer: 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_customer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_customer 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_customer. 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_customer 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 →