request_customer_merge · Shopify Graphql MCP: Risk & Policy

WHAT IT DOES

What request_customer_merge does on Shopify Graphql

AI agents use request_customer_merge to create or update resources in Shopify Graphql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shopify Graphql environment.

WHY IT NEEDS A POLICY

Why request_customer_merge needs a policy

Merging customers combines records including order history and addresses. While potentially reversible in some systems, customer merges are typically difficult to undo and have significant blast radius — merging the wrong customers could corrupt order history and customer data across a store.

From the tool's definition Merge one customer into another (combines order history, addresses, etc.)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

request_customer_merge Rate-limited

request_customer_merge 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": {
    "request_customer_merge": {
      "limits": [
        {
          "counter": "request_customer_merge_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 Shopify Graphql, so you can run agents against it safely.

FAQ

Questions about request_customer_merge

What does the request_customer_merge tool do? +

Merge one customer into another (combines order history, addresses, etc.). It is categorised as a Write tool in the Shopify Graphql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on request_customer_merge? +

Register the Shopify Graphql MCP server in PolicyLayer and add a rule for request_customer_merge: 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 Shopify Graphql. Nothing to install.

What risk level is request_customer_merge? +

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

Can I rate-limit request_customer_merge? +

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

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

request_customer_merge is provided by the Shopify Graphql MCP server (uvu-store/shopify-graphql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.