update_customer_card · Omise MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_customer_card does on Omise MCP Server

AI agents use update_customer_card 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_customer_card needs a policy

Updating a customer's card is a modification operation that changes stored payment method details. While reversible, this affects sensitive financial data and could enable payment method substitution if misused by an agent. The high severity reflects the sensitive nature of customer payment information and potential for fraud if an agent updates a card without proper authorization.

From the tool's definition Tool is named 'update_customer_card' with description 'Update a customer card'. This modifies customer payment card data, which is sensitive financial information. The action is reversible (a card can be updated again), making it Write rather than Destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_customer_card Rate-limited

update_customer_card 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_customer_card": {
      "limits": [
        {
          "counter": "update_customer_card_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_customer_card

What does the update_customer_card tool do? +

Update a customer card. 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_customer_card? +

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

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

Can I rate-limit update_customer_card? +

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

Set action: deny in the PolicyLayer policy for update_customer_card. 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_customer_card? +

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