Update an existing page
AI agents use update_page 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 modifies existing pages in a Shopify store, which is a reversible write operation. The high severity reflects that unauthorized page updates could deface the storefront, inject malicious content, alter product information, or harm customer trust. However, it is not Destructive (pages can be reverted), Financial (no money moves), or Execute (no arbitrary code execution).
From the tool's definition Tool name 'update_page' and description 'Update an existing page' indicate modification of existing data. The Shopify GraphQL context shows this operates on store pages, which are business-critical content assets.
Attacks that exploit this kind of access
Update an existing page. 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 update_page: 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.
update_page 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 update_page 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 update_page. 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.
update_page 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 →