Fetch customer events (page views, product views, searches, etc.)
AI agents call get_customer_events to retrieve information from Shopify Graphql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical customer activity data without creating, modifying, deleting, or executing external operations. The verb 'Fetch' and the passive nature of the data (events that have already occurred) confirm this is a read operation. The low severity reflects minimal blast radius—exposure of customer event data is a privacy concern but not immediately destructive or financial.
From the tool's definition Tool name 'get_customer_events' and description 'Fetch customer events' indicate a retrieval operation with no modification capability. The examples listed (page views, product views, searches) are all read-only events.
Attacks that exploit this kind of access
Fetch customer events (page views, product views, searches, etc.). It is categorised as a Read tool in the Shopify Graphql MCP Server, which means it retrieves data without modifying state.
Register the Shopify Graphql MCP server in PolicyLayer and add a rule for get_customer_events: 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.
get_customer_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_customer_events 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.
Set action: deny in the PolicyLayer policy for get_customer_events. 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.
get_customer_events 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →