Update a linked Shopify store
AI agents use sitebay_update_shopify_store to create or update resources in SiteBay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiteBay MCP Server environment.
The tool modifies existing data (Shopify store settings or configuration) in a reversible manner. While 'update' operations are typically Write category, the severity is elevated to 'high' because updates to e-commerce store configurations could impact customer-facing business operations, payment processing, or catalog visibility.
From the tool's definition Tool name explicitly states 'update' and description indicates modifying an existing Shopify store connection/configuration linked to the SiteBay platform.
Attacks that exploit this kind of access
Update a linked Shopify store. It is categorised as a Write tool in the SiteBay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_update_shopify_store: 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 SiteBay MCP Server. Nothing to install.
sitebay_update_shopify_store 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 sitebay_update_shopify_store 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 sitebay_update_shopify_store. 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.
sitebay_update_shopify_store is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →