Fetch checkout branding settings for the store
AI agents call get_checkout_branding_settings 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 checkout branding configuration data without creating, modifying, deleting, or executing operations. It poses minimal risk as it only queries non-sensitive store presentation settings. No financial transactions, destructive operations, or code execution are involved.
From the tool's definition Tool name is 'get_checkout_branding_settings' and description states 'Fetch checkout branding settings for the store'. The verb 'Fetch' and the read-only nature of retrieving branding configuration indicates a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch checkout branding settings for the store. 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_checkout_branding_settings: 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_checkout_branding_settings 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_checkout_branding_settings 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_checkout_branding_settings. 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_checkout_branding_settings 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 →