Proxy requests to Shopify Admin API
AI agents invoke sitebay_shopify_proxy to trigger actions in SiteBay MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool proxies arbitrary requests to the Shopify Admin API, which can perform a wide range of operations including reading, writing, and potentially financial actions (orders, payments, products). Since the tool acts as a proxy for arbitrary API requests, the actual operation depends on the request arguments. The most severe plausible misuse includes financial or destructive actions via the Shopify Admin API (e.g.
From the tool's definition Proxy requests to Shopify Admin API
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Proxy requests to Shopify Admin API. It is categorised as a Execute tool in the SiteBay MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_shopify_proxy: 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_shopify_proxy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sitebay_shopify_proxy 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_shopify_proxy. 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_shopify_proxy 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 →