Get visitor privacy consent status
AI agents call get_visitor_privacy_consent 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 existing privacy consent status data without modifying, creating, deleting, or executing any operations. It has no side effects and falls clearly into the Read category with low severity since it only accesses informational data about visitor consent.
From the tool's definition Tool name 'get_visitor_privacy_consent' and description 'Get visitor privacy consent status' indicate a retrieval operation. The verb 'Get' and absence of any modification, deletion, or execution language confirm read-only behavior.
Attacks that exploit this kind of access
Get visitor privacy consent status. 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_visitor_privacy_consent: 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_visitor_privacy_consent 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_visitor_privacy_consent 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_visitor_privacy_consent. 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_visitor_privacy_consent 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 →