Medium Risk

customer_data

CRUD operations for local customer data.

How to control customer_data ↓

What customer_data does on Shopify Storefront MCP Server

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

Medium Risk

Why customer_data needs a policy

CRUD (Create, Read, Update, Delete) spans multiple categories. The most severe non-destructive interpretation is Write (create/update), but Delete operations within CRUD could be Destructive. However, 'local customer data' suggests this may operate on a local cache/store rather than the live Shopify backend.

From the tool's definition CRUD operations for local customer data

Documented attack patterns abuse exactly the kind of access customer_data gives an agent:

How to control customer_data

PolicyLayer is an MCP gateway — it sits between your AI agents and Shopify Storefront MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for customer_data:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "customer_data": {
      "limits": [
        {
          "counter": "customer_data_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Shopify Storefront MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about customer_data

What does the customer_data tool do? +

CRUD operations for local customer data. It is categorised as a Write tool in the Shopify Storefront 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 customer_data? +

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

What risk level is customer_data? +

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

Can I rate-limit customer_data? +

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

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

customer_data is provided by the Shopify Storefront MCP Server MCP server (quentincody/shopify-storefront-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shopify Storefront MCP Server tool call.

Start from Shopify Storefront MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

3 Shopify Storefront MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.