delete_payment_customization

Delete a payment customization

Server Shopify Graphql uvu-store/shopify-graphql-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_payment_customization does on Shopify Graphql

AI agents call delete_payment_customization to permanently remove resources in Shopify Graphql — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_payment_customization needs a policy

Deletion is an irreversible operation that cannot be undone. Payment customizations are critical business configuration affecting how payments are processed. While not directly moving money (Financial), the destruction of payment rules/settings that merchants rely on creates significant blast radius—a mistaken deletion could disrupt payment processing, refund rules, or discount applications.

From the tool's definition Tool name is 'delete_payment_customization' and description states 'Delete a payment customization'. The verb 'delete' combined with 'payment customization' indicates irreversible removal of configuration data that controls payment processing in a Shopify…

Questions about delete_payment_customization

What does the delete_payment_customization tool do? +

Delete a payment customization. It is categorised as a Destructive tool in the Shopify Graphql MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_payment_customization? +

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

delete_payment_customization is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_payment_customization? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.