create_recipient · Omise MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_recipient does on Omise MCP Server

AI agents use create_recipient 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.

WHY IT NEEDS A POLICY

Why create_recipient needs a policy

This tool creates a new recipient entity that enables financial transfers. While creation itself is reversible (Write rather than Destructive), the severity is high because creating a recipient establishes a payment pathway that could be abused to redirect funds to attacker-controlled accounts.

From the tool's definition The tool name is 'create_recipient' and description states it will 'Create a new recipient for transfers'. This creates a new data record in the Omise payment system that can be used for subsequent financial transfers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_recipient Rate-limited

create_recipient stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_recipient": {
      "limits": [
        {
          "counter": "create_recipient_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Omise MCP Server, so you can run agents against it safely.

FAQ

Questions about create_recipient

What does the create_recipient tool do? +

Create a new recipient for transfers. 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.

How do I enforce a policy on create_recipient? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for create_recipient: 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.

What risk level is create_recipient? +

create_recipient is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_recipient? +

Yes. Add a rate_limit block to the create_recipient 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.

How do I block create_recipient completely? +

Set action: deny in the PolicyLayer policy for create_recipient. 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.

What MCP server provides create_recipient? +

create_recipient 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.