set_payment_customization_activation

WHAT IT DOES

What set_payment_customization_activation does on Shopify Graphql

AI agents use set_payment_customization_activation to create or update resources in Shopify Graphql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shopify Graphql environment.

WHY IT NEEDS A POLICY

Why set_payment_customization_activation needs a policy

This tool modifies payment customization states (activate/deactivate) but does not directly move money or create financial obligations, placing it in Write rather than Financial. However, it affects payment processing rules which could have significant business impact if misconfigured by an AI agent.

From the tool's definition Tool name 'set_payment_customization_activation' combined with description 'Activate or deactivate multiple payment customizations' indicates modification of payment system configuration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_payment_customization_activation Rate-limited

set_payment_customization_activation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_payment_customization_activation": {
      "limits": [
        {
          "counter": "set_payment_customization_activation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Shopify Graphql, so you can run agents against it safely.

FAQ

Questions about set_payment_customization_activation

What does the set_payment_customization_activation tool do? +

Activate or deactivate multiple payment customizations. It is categorised as a Write tool in the Shopify Graphql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_payment_customization_activation? +

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

set_payment_customization_activation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_payment_customization_activation? +

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

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

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