merge_customers · AdminAgent MCP: Risk & Policy

WHAT IT DOES

What merge_customers does on AdminAgent

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

WHY IT NEEDS A POLICY

Why merge_customers needs a policy

This tool modifies customer data by consolidating records, which is a Write operation. Severity is high because customer merging can affect order history, contact information, loyalty programs, and customer identification across the store, creating confusion or data integrity issues if misapplied.

From the tool's definition Tool name 'merge_customers' indicates combining or consolidating customer records. The server context describes 'full store management' via Shopify Admin API integration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_customers Rate-limited

merge_customers 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": {
    "merge_customers": {
      "limits": [
        {
          "counter": "merge_customers_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 AdminAgent, so you can run agents against it safely.

FAQ

Questions about merge_customers

What does the merge_customers tool do? +

merge_customers. It is categorised as a Write tool in the AdminAgent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_customers? +

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

What risk level is merge_customers? +

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

Can I rate-limit merge_customers? +

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

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

merge_customers is provided by the AdminAgent MCP server (rushikeshmore/admin-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.