Create a new return from an order
AI agents use create_return 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.
This tool creates (writes) a new return entity tied to an existing order, modifying store state reversibly. While returns can have financial implications (refunds), the tool itself is a data creation operation rather than moving money directly; the severity is medium because misuse could create unauthorized returns affecting inventory and customer relations, but the operation is reversible through normal return…
From the tool's definition Tool name 'create_return' and description 'Create a new return from an order' indicate a create operation that adds a new return record to a Shopify store's system.
Attacks that exploit this kind of access
Create a new return from an order. 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.
Register the Shopify Graphql MCP server in PolicyLayer and add a rule for create_return: 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.
create_return 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 create_return 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 create_return. 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.
create_return 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 →