shopify_create_product
AI agents use shopify_create_product to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
This tool creates new product records in Shopify, a production e-commerce system. While creation is reversible (products can be deleted), the high severity reflects the operational impact: uncontrolled product creation could flood a store with unwanted listings, affect inventory systems, disrupt customer experience, and require manual cleanup.
From the tool's definition Tool name 'shopify_create_product' explicitly indicates creation of a product resource on the Shopify platform. The 'create' verb and Shopify context (e-commerce/SaaS platform) establish this as a data creation operation.
Attacks that exploit this kind of access
shopify_create_product. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for shopify_create_product: 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 Integrations MCP. Nothing to install.
shopify_create_product is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the shopify_create_product 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 shopify_create_product. 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.
shopify_create_product is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →