New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_visitor_privacy_consent

Get visitor privacy consent status

SERVERShopify Graphql SOURCEuvu-store/shopify-graphql-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/uvu-store-shopify-graphql-mcp/get-visitor-privacy-consent.md

What get_visitor_privacy_consent does on Shopify Graphql

AI agents call get_visitor_privacy_consent to retrieve information from Shopify Graphql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_visitor_privacy_consent is rated Low

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.

Questions about get_visitor_privacy_consent

What does the get_visitor_privacy_consent tool do? +

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.

How do I enforce a policy on get_visitor_privacy_consent? +

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.

What risk level is get_visitor_privacy_consent? +

get_visitor_privacy_consent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_visitor_privacy_consent? +

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.

How do I block get_visitor_privacy_consent completely? +

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.

What MCP server provides get_visitor_privacy_consent? +

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.

More on Shopify Graphql, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Shopify Graphql's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.