update_recipient · Omise MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_recipient does on Omise MCP Server

AI agents use update_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 update_recipient needs a policy

This tool modifies recipient data reversibly (an update operation), which falls under Write category. However, the severity is elevated to 'high' rather than the typical medium for Write operations because recipients in payment systems store sensitive financial information (bank accounts, routing details) and misconfiguration could redirect funds to wrong accounts or enable fraudulent transfers.

From the tool's definition Tool name 'update_recipient' and description 'Update recipient information' indicate modification of existing recipient data. The broader server context shows this is part of Omise's payment processing API that handles transfers and financial operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_recipient Rate-limited

update_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": {
    "update_recipient": {
      "limits": [
        {
          "counter": "update_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 update_recipient

What does the update_recipient tool do? +

Update recipient information. 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 update_recipient? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for update_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 update_recipient? +

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

Can I rate-limit update_recipient? +

Yes. Add a rate_limit block to the update_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 update_recipient completely? +

Set action: deny in the PolicyLayer policy for update_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 update_recipient? +

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