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

get_checkout

Fetch a specific checkout by ID

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-checkout.md

What get_checkout does on Shopify Graphql

AI agents call get_checkout 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_checkout is rated Low

This tool retrieves checkout information by ID without creating, modifying, executing operations, or deleting data. Fetching checkout data is a read-only operation with no side effects. Severity is low because reading checkout data poses minimal risk—it does not expose sensitive payment information (GraphQL APIs typically exclude PCI-regulated data) and does not allow modification of orders or financial transactions.

From the tool's definition Tool name 'get_checkout' with description 'Fetch a specific checkout by ID' indicates data retrieval without modification.

Questions about get_checkout

What does the get_checkout tool do? +

Fetch a specific checkout by ID. 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_checkout? +

Register the Shopify Graphql MCP server in PolicyLayer and add a rule for get_checkout: 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_checkout? +

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

Can I rate-limit get_checkout? +

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

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

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