Revoke a customer
AI agents call revoke_customer_payment_method 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.
Revoking a payment method is a destructive, non-reversible action. Once revoked, the customer's saved payment method is permanently invalidated and cannot be restored. This has high blast radius as it could disrupt recurring billing, subscriptions, or future purchases for affected customers. Confidence is slightly reduced because the description is truncated and incomplete.
From the tool's definition 'Revoke a customer [payment method]' — revoking a payment method permanently removes/invalidates it, which is an irreversible action on a customer's stored payment credential
Attacks that exploit this kind of access
Revoke a customer. 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.
Register the Shopify Graphql MCP server in PolicyLayer and add a rule for revoke_customer_payment_method: 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.
revoke_customer_payment_method is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_customer_payment_method 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 revoke_customer_payment_method. 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.
revoke_customer_payment_method 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 →